Thank you for your donation!


Permanent HTTP 'refused to connect' - new install
#1
Version is current, fresh install, compile in place method.

Can login to prompt locally, can ssh in, but get 'refused' with http://moode.local & with IP. http://moode gives IP not found.

Multiple attempts: lastly I plugged all devices direct to DHCP enabled router, had expected range IP (192.168.1.105) for Pi, same result, can’t think how to make it simpler.

I'm new to moodeaudio & not very network or Linux savvy and would appreciate advice as out of ideas,

Thank you, folks.
Reply
#2
So you're saying an SSH client can connect to the Pi's IP address (let's forget dns for now) on port 22 (ssh) but a web browser cannot connect to the same IP on port 80 (http)?

Assuming your Pi's IP address is 192.168.1.105, are you getting the error when trying to load http://192.168.1.105 in your web browser?
Reply
#3
I have not specified ports, though believe those to be default?

⇨ Yᴇs ⇦ that is what I am experiencing Undecided

And the error reports 'refused' rather than not resolved.
Reply
#4
@robdean

Harkening back to your first post, you said "Version is current, fresh install, compile in place method."

To me, "compile in place method" means you built moOde yourself from the build recipe. 

If this is true, then I advise you to stop what you're doing and install moOde from the image available for download on the moodeaudio.org home page. There's too many places someone new to the build process can go wrong. Installing successfully from the image is drop-dead easy by comparison.

Regards,
Kent
Reply
#5
(08-11-2020, 03:52 PM)robdean Wrote: I have not specified ports, though believe those to be default?

⇨ Yᴇs ⇦ that is what I am experiencing Undecided

And the error reports 'refused' rather than not resolved.

Calm... I'm just clarifying your issue and the symptoms.
A hostname can still resolve but point to the wrong IP, for example if your Pi's IP is not reserved on the router and it has changed and something else has picked up that address.

So, if you can ssh to the Pi's IP you could see if nginx is actually listening on port 80 by running;

Code:
sudo netstat -lp | grep http

If nothing comes back the web server's not running and the problem is with the OS image, reflash with a fresh image. If Kent is right and you've attempted to build your own image then use a prebuilt image.
If nginx is running and shows as listening on 0.0.0.0:http then the issue is more likely to be an issue originating on your lan or the web browser.
Reply


Forum Jump: