PlexMediaServer Web Access

[Jath]

I apologize. I'm running FreeNAS in a VM. It is not metal. Along with that, I am not using IPv6.

I still can't access it after making those changes. Here's the below config and ping stats.

Ping from FreeNAS

[root@freenas ~]# ping 192.168.11.50
PING 192.168.11.50 (192.168.11.50): 56 data bytes
64 bytes from 192.168.11.50: icmp_seq=0 ttl=64 time=0.022 ms
64 bytes from 192.168.11.50: icmp_seq=1 ttl=64 time=0.039 ms
^C
--- 192.168.11.50 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.022/0.030/0.039/0.008 ms
[root@freenas ~#

Ping from my computer.

C:\Users\*>ping 192.168.11.50

Pinging 192.168.11.50 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.11.50:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Steven>

 

[JoeBeaver]

On your freenas box, what does /var/log/messages say when you turn on plexmediaserver_1?

Also, do you have promiscuous mode enabled in your ESX network config?
http://kb.vmware.com/selfservice/mi...ype=kc&docTypeID=DT_KB_1_1&externalId=1004099

 

[Jath]

I got the following when starting. This is from the console from the bottom of the screen, which looks similar to your other post, so I assume it's the /var/log/messages item.

Jan 26 16:44:03 freenas notifier: Performing sanity check on nginx configuration:
Jan 26 16:44:03 freenas notifier: nginx: the configuration file /usr/local/etc/nginx/nginx.conf syntax is ok
Jan 26 16:44:03 freenas notifier: nginx: configuration file /usr/local/etc/nginx/nginx.conf test is successful
Jan 26 16:44:03 freenas notifier: Stopping avahi-daemon.
Jan 26 16:44:04 freenas kernel: bridge0: Ethernet address: 02:9a:9c:99:05:00
Jan 26 16:44:04 freenas kernel: bridge0: link state changed to UP
Jan 26 16:44:04 freenas kernel: em0: promiscuous mode enabled
Jan 26 16:44:04 freenas kernel: epair0a: Ethernet address: 02:62:f0:00:05:0a
Jan 26 16:44:04 freenas kernel: epair0b: Ethernet address: 02:62:f0:00:06:0b
Jan 26 16:44:04 freenas kernel: epair0a: link state changed to UP
Jan 26 16:44:04 freenas kernel: epair0b: link state changed to UP
Jan 26 16:44:04 freenas kernel: epair0a: promiscuous mode enabled
Jan 26 16:44:05 freenas ntpd[1838]: bind() fd 22, family AF_INET6, port 123, scope 5, addr fe80::62:f0ff:fe00:50a, mcast=0 flags=0x11 fails: Can't assign requested address
Jan 26 16:44:05 freenas ntpd[1838]: unable to create socket on epair0a (467) for fe80::62:f0ff:fe00:50a#123
Jan 26 16:44:11 freenas kernel: ifa_del_loopback_route: deletion failed
Jan 26 16:44:11 freenas kernel: Freed UMA keg (udp_inpcb) was not empty (20 items). Lost 2 pages of memory.
Jan 26 16:44:11 freenas kernel: Freed UMA keg (udpcb) was not empty (168 items). Lost 1 pages of memory.
Jan 26 16:44:11 freenas kernel: Freed UMA keg (tcptw) was not empty (50 items). Lost 1 pages of memory.
Jan 26 16:44:11 freenas kernel: Freed UMA keg (tcp_inpcb) was not empty (30 items). Lost 3 pages of memory.
Jan 26 16:44:11 freenas kernel: Freed UMA keg (tcpcb) was not empty (20 items). Lost 5 pages of memory.
Jan 26 16:44:11 freenas kernel: hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Jan 26 16:44:11 freenas kernel: hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required

 

[JoeBeaver]

Did you try enabling prom. mode in ESX?

 

[Jath]

And there we go. Prom mode got it to work.

Thank you VERY much, Joe. Some freakin' awesome help right there. I didn't even think of Prom mode since everything else was working on that.

Thanks again!

 

[chrisjbarry]

On your freenas box, what does /var/log/messages say when you turn on plexmediaserver_1?

Also, do you have promiscuous mode enabled in your ESX network config?
http://kb.vmware.com/selfservice/mi...ype=kc&docTypeID=DT_KB_1_1&externalId=1004099

Thanks for this response to this thread. This was my issue all along, and driving me crazy for days.


Sent from pay phone in the airport.