The Unraid server is unreachable from outside your network. (Yep another one of these :s)


Go to solution Solved by tylah337,

Recommended Posts

The Unraid server is unreachable from outside your network. Be sure you have configured your router to forward port redacted/TCP to the Unraid server at redacted port 443.
Was working perfectly fine till i updated from 6.10.rc4 to 6.10.3. Deleted addon deleted config files, disabled ipv6 and so on, 0 luck so far pls help ~

Link to comment

Unraid OS 6.10.3 with My Servers plugin version 2022.05.24.1752
 Signed in to Unraid.net as tylah337
Use SSL is no
 Rebind protection is disabled for myunraid.net
Local Access url: http://XeonWorkstation.local
 192-168-1-9.hash.myunraid.net resolves to 192.168.1.9
Remote Access url: https://[redacted].hash.myunraid.net:[redacted]
 [redacted].hash.myunraid.net resolves to [redacted]

Request:
{
    "keyfile": "[redacted]",
    "plgversion": "2022.05.24.1752",
    "internalhostname": "XeonWorkstation.local",
    "internalport": "80",
    "internalprotocol": "http",
    "remoteaccess": "yes",
    "servercomment": "Medical",
    "servername": "XeonWorkstation",
    "internalip": "192.168.1.9",
    "externalhostname": "*.hash.myunraid.net",
    "externalport": "[redacted]",
    "externalprotocol": "https"
}
Response (HTTP 200):
[]
success

Link to comment

As a first check, are you having any issues provisioning the SSL certificate? There were problems over the weekend, see https://forums.unraid.net/topic/126105-ssl-cert-error-im-an-unraid-noob/#comment-1150163

 

 

If the certificate is fine then this sounds like a port forwarding issue.

 

Run this command with two v's to get the non-anonymized output:

php /usr/local/emhttp/plugins/dynamix/include/UpdateDNS.php -vv

(don't post it here)

 

What you are looking for is the non-anonymized Remote Access url. Try to access that url from a phone or other system not on your local network to see what the error message is. If you would like me to test, please send me the non-anonymized output (and a link to this thread) in a DM.

  • Like 1
Link to comment
  • Solution

For anyone stumbling upon this thread, it was a port forwarding issue (swapped to fiber a while ago and had to ask my ISP to reconfigure port forwarding on their side). Now the addon works perfectly.

Edited by tylah337
  • Like 1
Link to comment
  • 1 year later...
  • 3 weeks later...
Posted (edited)

as far as i recall i asked them to check the ports that i was using and they realised as well that they were unaccesible and then what they did was on their part i dont really recall sadly, it was someting to do with asking them to allow port forwarding to happen on their end.

Edited by tylah337
Link to comment