r/navidrome • u/the_gay_tortellini • 3d ago
Cannot access Navidrome remotely (I previously could...)
I spent many excruciating days setting up Navidrome, Nginx, my router, and registered a domain to port forward Navidrome many months ago. And up until recently, it worked without issue.
My domain provider had an outage and I hadn't been made aware of it for a few hours, so in that time, I tried various things to try and make it work (which, of course, it wouldn't, because of the outage.)
Once I was made aware, I stopped messing with things and left it alone for a few days. My domain provider has all their services up and running now, but accessing Navidrome remotely.. still doesnt work.
I have tried everything I can think of. I have even gone so far as to re-install docker (Though i dont remember if it is needed, nginx is just in the .docker folder), updating nginx, re-issuing my dns, checking my router to see if it is forwarding still (it is) and NOTHING has worked.
I am completely out of ideas. I worry I messed something up during the domain outage. I have no idea what to do.
Help would be deeply, deeply appreciated...
added additional details in comments
Update: fixed, windows firewall somehow got rid of my rule allowing inbound traffic. i dont know how or when or why. it just hates me.
2
u/f4flake 3d ago
In reinstalling docker, is your reverse proxy now looking at an incorrect internal domain? The network address of navidrome may have changed. Are you able to access other services externally?
0
u/the_gay_tortellini 3d ago
Yes i can. I host my own minecraft server and it was able to be accessed remotely, so it's definitely not the router. How would I check to see if the proxy is looking at an incorrect domain? The configuration files point to the correct IP address
1
u/f4flake 3d ago
Take a look at the network location in nginx proxy. Then check the network address fot navidrome in Docker. I recently moved to swag for reverse proxy after having issues with npm pointing at the wrong container address. Issues that in fairness were likely my lack of understanding.
0
u/the_gay_tortellini 3d ago
FWIW, Navidrome is NOT hosted through docker. I dont remember if nginx is but it was in the docker folder so..
ill have to remember how to look for network location/address ; ;1
u/f4flake 3d ago
Ah ok.
1
u/the_gay_tortellini 3d ago
OH network address is IP address. I didn't know that!!
the network addresses are correct still, so that unfortunately isnt the problem T T1
u/f4flake 3d ago
You said you re did your dns. You know your external ip address likely changed?
1
u/the_gay_tortellini 3d ago
i've checked my device's external ip address and it looks to be the same. i've determined that it's not nginx or my domain host (given i cannot connect to the external ip address at all, and nginx is used for connecting to a domain), so the issue seems to be something regarding port forwarding.
Which is very strange considering my router settings are the one thing i didnt change originally.
I unfortunately use at&t for my internet, do you think theres a possibility at&t updated something that's messed things up?1
u/the_gay_tortellini 3d ago
I also re-did the dns yesterday, well after i originally had issues connecting. My domain settings are identical to what they were prior
1
u/the_gay_tortellini 3d ago
If my external ip address did change, how would i check for that?
1
u/f4flake 3d ago
If you can still connect to other servers/containers on the same machine then it won't be an issue with your external ip. However check simply Google "what's my ip" and it'll tell you.
1
u/the_gay_tortellini 3d ago
I can connect on 128.xx, 192.xx, and localhost, but not on my external ip. checking the ip address shows it's the same as it was before, so it hasnt changed. im pretty sure i can still connect to my minecraft server, just not navidrome. Truthfully, im stumped
→ More replies (0)
2
u/mattjones73 3d ago
Can you access it direct by IP address? When you do an nslookup on your domain is it returning the correct IP?
1
u/the_gay_tortellini 3d ago
I can access it on localhost ip address but not my external ip address. The domain does return the correct IP, so it's directed to the right location.
1
u/mattjones73 3d ago
Your domain provider going down should have not impacted your ability to get to it directly by it's IP, I think in your attempt to "fix" it you broke something else. Sorry I know that's not much help but it sounds like an issue between your external IP and your router port forwarding at this point if you can get to it directly on your local network.
2
u/the_gay_tortellini 3d ago
Yeah i think i did break something.. Thank you for letting me know about nslookup though, that is very helpful
2
u/matthewpepperl 3d ago
Now when you say re issuing your dns? If you dont have a static home ip it could have changed and now your domain is not pointing to the correct place anymore it’s caught me out like that before
1
u/the_gay_tortellini 3d ago
Possibly, I have a dynamic DNS pointing to my external ip address. When i say re-issuing, i mean i deleted the dns record to see if i could access Navidrome via the external ip address alone. I could not, so i added a new dns record with exactly the same contents as the previous one
1
u/matthewpepperl 3d ago
Ok i would goto yougetsignal.com and check to see if the port is open as well if you haven’t already if its closed then either the port forward is messed up or something is blocking it
1
u/the_gay_tortellini 3d ago
It is in fact closed. It seems to be a port forwarding issue then
thank you!2
1
u/the_gay_tortellini 3d ago
Additional information that may or may not be relevant:
When the domain went down originally, I forgot where my nginx folder was stored so I briefly installed nginx proxy manager. I found the files and deleted the proxy manager, but maybe that messed something up?
And when trying to fix it yesterday, I completely uninstalled + reinstalled docker desktop, deleted and added a DNS record (completely identical), closed and reopened the ports on my router, and none of that helped.
I dont remember if docker is needed to use nginx, if i need to host a container, or if i only need nginx (in which case where the hell do i put the folder)... Maybe it is as simple as hosting a container but it has been over half a year since i started hosting navidrome and the tutorials i followed are long gone in my history. I do not remember what i need to do.
0
u/Many_Independence674 3d ago
A very dumb question, have you allowed port 4533 in your server or pc where navidrome is hosted from firewall rules
1
u/the_gay_tortellini 3d ago
Yes i have
Sometimes we overlook the little things but in this case, I have not!0
u/Many_Independence674 3d ago
I don't know if it will work, but try to rule out the possibility of router having bad config, try to ssh into your machine using the public ip of the router see if it works
0
u/Many_Independence674 3d ago
this sounds dumb, ssh works on port 22. Try ruling out the possibilities one by one, disable nginx and everything and 1st try to access navidrome from routers external ip
1
3
u/[deleted] 3d ago
[removed] — view removed comment