First of all, I want to mention that the node is properly working and that this is not urgent*
Everything started to go wrong after I realized how having my NAS (which hosts Stor-J) in a DMZ was a frigging bad Idea. So, I put my unraid machine out of dmz and take the opportunity to specify to my already existing stor-j storage share to no exclude the second disk since only the first one was allowed and, well, that was redundant. BOOM as expected, dashboard down. After rebooting the docker with no success, i rebooted the NAS, with no much success either. After that point, even the whole machine seemed offline, since no ssh, no ping nor connection attempts to the NAS GUI worked BUT after some time trying to figure out what happened, everything came back in order… WEIRD
Anyway, I’m not here to talk about some weird unraid bugs but the aftermaths of what happened…
The thing is, the stor-j dashboard no longer uses the same IP as the NAS!
my local NAS IP is 192.168.2.13
but connecting to 192.168.2.13:14002 returns an unothorized connection (inaccessible)
And god knows how, I stumbled upon 127.0.0.1:14002 and well, that’s my good ol’ dashboard! (working)
Needless to say that this ip is out of my ip range / subnet and that it does not show as a device on my rooter / modem…
okok, where is the problem then I hear you asking!
I simply can’t access it on my local network, at all! The only way to access it is via the NAS itself (using the GUI boot)
Anyway to get it back online on my local network?
Some info that could be relevant:
Internet adress of the docker is tied to my DDNS which is correctly working
The network type of the docker is set on Bridge
There shouldn’t be any firewall problem
Oh and don’t worry, I didn’t get hacked after more than 40 000 loging attempts! Stay safe and use a strong password, my password manager saved my bacon here!
Thank you for the incoming help <3