2019-09-16, 01:17 AM
This is my first Linux NextPVR install. Used the wget & sudo apt install first with no web server. Second, installed and used curl, still a 404 local host. Please help!
2019-09-16, 01:17 AM
This is my first Linux NextPVR install. Used the wget & sudo apt install first with no web server. Second, installed and used curl, still a 404 local host. Please help!
2019-09-16, 08:52 AM
A 404 suggests the web server is running. Make sure JavaScript is enabled and hit Ctrl f5
2019-09-16, 01:12 PM
Sorry, its "Unable to Connect" Is that a different issue?
2019-09-16, 02:47 PM
Yes do you see anything of note when you type
sudo service nextpvr-server status Martin
2019-09-16, 05:12 PM
Does it make any difference if you explicitly ask for the index.html page? ie, http://ip:8866/index.html
2019-09-16, 07:03 PM
nextpvr-server.service - NextPVRServer
Loaded: loaded (/lib/systemd/system/nextpvr-server.service; enabled; vendor p Active: inactive (dead) since Mon 2019-09-16 13:54:43 CDT; 4min 21s ago Process: 1416 ExecStart=/opt/nextpvr/shell/server.sh start (code=exited, statu Sep 16 13:54:41 luther-122 systemd[1]: Starting NextPVRServer... Sep 16 13:54:41 luther-122 server.sh[1416]: Starting server../opt/nextpvr/shell/ Sep 16 13:54:43 luther-122 server.sh[1416]: Done. PID= Sep 16 13:54:43 luther-122 systemd[1]: nextpvr-server.service: Succeeded. Sep 16 13:54:43 luther-122 systemd[1]: Started NextPVRServer. Samething after sudo service nextpvr-server start
2019-09-18, 08:16 PM
How do I diagnose the server not starting? Thanks for the help!
2019-09-18, 09:19 PM
If you got a 404 back, that means the server was running, in which case try adding the "index.html" to the url:
http://ip:8866/index.html While it shouldn't require this index.html part of the url, some have needed to, and I haven't got to the bottom of why yet.
2019-09-20, 03:51 AM
index.html wasn't different. I'm not sure the server is running? I did stop/start then status and this is the reply.
Active: inactive (dead) since Thu 2019-09-19 22:47:37 CDT; 5s ago Also, Chrome says: This site can’t be reached 127.0.0.1 refused to connect. Does that help?
2019-09-20, 04:19 AM
if you do a netstat -a | grep 8866 and you get a line returned with 8866 then most likely web listener is up and running, otherwise it is not.
|
|