setup web page unavailable?

[sector327 4]

Well I'm just getting into this & I'm very excited! This has been needed for a long, long time

 

Hopefully this is simple.  I have a server (Fedora26 server) located at 192.168.1.250. I do not have a gui installed on it and do all my administration remotely via ssh. I use cockpit a little just to see what's going on and the load on the server. it uses port 9090 and it displays fine.  I installed emby and rebooted. Everything looks fine I guess but when I try to access the setup page at 192.168.1.250:8096 it shows as "site cant be reached" which is odd since the 9090 port shows fine. 

 

Any hints on how to proceed? thanks for any help. I'm really enjoying learning.

 

Some info that might help:

fedora 26 server installed (no gui installed)

samba running fine

selinux disabled (set to zero & smb restarted) (yeah....I need to get it turned off automatically if reboot or fix the selinux sharing issue)

 

[dcrdev 255]

Well I'm just getting into this & I'm very excited! This has been needed for a long, long time

 

Hopefully this is simple.  I have a server (Fedora26 server) located at 192.168.1.250. I do not have a gui installed on it and do all my administration remotely via ssh. I use cockpit a little just to see what's going on and the load on the server. it uses port 9090 and it displays fine.  I installed emby and rebooted. Everything looks fine I guess but when I try to access the setup page at 192.168.1.250:8096 it shows as "site cant be reached" which is odd since the 9090 port shows fine. 

 

Any hints on how to proceed? thanks for any help. I'm really enjoying learning.

 

Some info that might help:

fedora 26 server installed (no gui installed)

samba running fine

selinux disabled (set to zero & smb restarted) (yeah....I need to get it turned off automatically if reboot or fix the selinux sharing issue)

 

Firstly if you are using the packages from the home page, you do not need selinux disabled.

 

A few debugging steps:

systemctl status emby-server
firewall-cmd --list-services

Post the output of those two here.

 

^ If emby-server is in a failed state - I bet I know why as well:

mkdir /var/lib/emby && chown -R emby:emby /var/lib/emby

Edited December 13, 2017 by dcrdev

[sector327 4]

Thanks.  I disabled selinux as if it's running then the samba shares won't even work. There are commands to supposedly address that but they haven't yet. Don't worry about it. For now, I'm just turning selinux off. 

 

anyways the outputs:

● emby-server.service - Emby Server is a personal media server with apps on just about every device.
   Loaded: loaded (/usr/lib/systemd/system/emby-server.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2017-12-13 13:06:01 CST; 54min ago
 Main PID: 765 (EmbyServer)
    Tasks: 11 (limit: 4915)
   CGroup: /system.slice/emby-server.service
           └─765 /opt/emby-server/system/EmbyServer -programdata /var/lib/emby -ffmpeg /opt/emby-server/bin/ffmpeg -ffprobe /opt/emby-server/bin/ffprobe -updatepackage emby-server-rpm_{version}_x86_64.deb

Dec 13 13:06:25 localhost.localdomain emby-server[765]: Info App: Entry point completed: Emby.Security.PluginSecurityManager. Duration: 0.0001564 seconds
Dec 13 13:06:25 localhost.localdomain emby-server[765]: Info App: Starting entry point Emby.Server.Sync.SyncManagerEntryPoint
Dec 13 13:06:25 localhost.localdomain emby-server[765]: Info App: Sqlite version: 3.21.0
Dec 13 13:06:25 localhost.localdomain emby-server[765]: Info App: Sqlite compiler options: COMPILER=gcc-6.3.0,ENABLE_COLUMN_METADATA,ENABLE_DBSTAT_VTAB,ENABLE_FTS3,ENABLE_FTS3_PARENTHESIS,ENABLE_FTS3_TOKENIZER,ENABLE_FTS5,ENABLE_JSON1,ENABLE_PREUPDATE_HOOK,ENABLE_RTREE,ENABLE_SESSION,ENABLE_UNLOCK_NOTIFY,ENABLE_UPDATE_DELETE_LIMIT,LIKE_DOESNT_MATCH_BLOBS,MAX_SCHEMA_RETRY=25,MAX_VARIABLE_NUMBER=250000,OMIT_LOOKASIDE,SECURE_DELETE,THREADSAFE=1
Dec 13 13:06:25 localhost.localdomain emby-server[765]: Info App: Default journal_mode for /var/lib/emby/data/sync14.db is wal
Dec 13 13:06:25 localhost.localdomain emby-server[765]: Info App: PRAGMA synchronous=1
Dec 13 13:06:25 localhost.localdomain emby-server[765]: Info App: Entry point completed: Emby.Server.Sync.SyncManagerEntryPoint. Duration: 0.1158659 seconds
Dec 13 13:06:25 localhost.localdomain emby-server[765]: Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint
Dec 13 13:06:25 localhost.localdomain emby-server[765]: Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0024318 seconds
Dec 13 13:06:25 localhost.localdomain emby-server[765]: Info App: All entry points have started


and firewall output is:

ssh dhcpv6-client cockpit samba

[Luke 42078]

why not just use the default 8096 port?

[dcrdev 255]

Lost access to my server - so can't recall if the firewall rule is called emby or emby-server, you may need to substitute them below:

firewall-cmd --add-service emby
firewall-cmd --add-service emby --permanent
firewall-cmd --reload

why not just use the default 8096 port?

He is - he was referring to port 9090 for cockpit, it's a web based server management tool by Redhat.

Edited December 13, 2017 by dcrdev

[sector327 4]

BAM!  Thanks dcrdev!  (btw, its emby-server)

 

I can see it now. Now to tinker in my free time and see what I can get going. It's been a long long time since I've worked w/ Linux (before selinux existed) so I was used to iptables. And even then, the firewalls were much less involved.

[dcrdev 255]

@@Luke worth noting here that Fedora and RHEL do not share the same default zone... it's not going to work out the box across all platforms Fedora Workstation uses "FedoraWorkstation", Fedora server uses "FedoraServer" and RHEL uses "public". Something that might have been picked up if you were publishing the source packages as per the GPL and/or they were actually being tested.

[alucryd 315]

The package does not touch any firewall configuration, it's up to the user to know which firewall they're using and how to forward a port through it, a package should not open a hole in any given system behind one's back. People installing these kind of things on a machine designed to be accessed remotely should be able to deal with this.

 

Furthermore, the package is installable on many RPM distros, and not all of them use firewalld, it ships a firewalld config file for convenience though (it's called emby-server btw).

Edited December 15, 2017 by alucryd

[dcrdev 255]

The package does not touch any firewall configuration, it's up to the user to know which firewall they're using and how to forward a port through it, a package should not open a hole in any given system behind one's back. People installing these kind of things on a machine designed to be accessed remotely should be able to deal with this.

 

Furthermore, the package is installable on many RPM distros, and not all of them use firewalld, it ships a firewalld config file for convenience though (it's called emby-server btw).

 

Beg to differ...

 

What do the instructions say on the homepage:

Install
yum install emby-server-rpm_3.2.50.0_x86_64.rpm
Run Setup Wizard
Visit http://localhost:8096

My experience has been that on CentOS atleast, installing the package automatically is adding it to the public zone. I mentioned this previously, in the sense that it's a bit nefarious - but it was ignored. 

• Is firewalld installed and running by default on even the most minimal Fedora/RHEL installs - check.
• Is firewalld configured out of the box to allow most known services to run unhindered - check.
• Therefore is the average user likely to know that they have firewalld installed - nope.
• Is there anything in the documentation anywhere to suggest that the package includes a firewalld config - nope.

Additionally worth pointing out that the included config doesn't allow for dlna - easy enough to sort.

[alucryd 315]

• OpenSuse, among others, does not have firewalld installed by default
• emby does not qualify as one of the most known services
• The average user installing a server application should be familiar with firewall basics
• We will add some instructions on the website

The next version will include the udp ports in the config file for dlna, thx for pointing that out.

[sector327 4]

 

• OpenSuse, among others, does not have firewalld installed by default
• emby does not qualify as one of the most known services
• The average user installing a server application should be familiar with firewall basics
• We will add some instructions on the website

The next version will include the udp ports in the config file for dlna, thx for pointing that out.

 

 

 

Thanks. I must say from the initial response, it was almost like a "rtfm" which I admit isn't overly helpful. THIS however is very good news. I'm more knowledgeable than I sometimes care to admit and if there was documentation then I would have at least tried that first. As dcrdev and you even acknowledged, there's essentially no obvious pointer on the website for where to find instructions/manual type pages. Adding them or even just a simple "FQA/Check these things if it doesn't work" type document is a good thing.

 

Basically I'm glad to see I somehow shined a light on a possible weakness in the process. I helped I guess & I hope to help more in different ways wherever I can in the future.