6.5.3 Enabling SSL broke my server

[alexfsr]

Just upgraded from 6.3.3 and decided to enable SSL. The intention was to use a self-signed cert and keep the server inside my local network.

The moment i switched SSL to Yes i lost connection to my server. It redirects to "homenas.local" bullsh*t that windows cannot resolve because the f*ck is that???

I cannot connect to the server's web interface now. How do i disable this shit from a local terminal on the server machine itself to restore connectivity?

 

***The server has critical data on it and i'm super pissed.

[JonathanM]

You can always use the IP address instead of the hostname.

[alexfsr]

5 minutes ago, jonathanm said:

You can always use the IP address instead of the hostname.

I always do that. But after i enabled SSL it redirects to this "homenas.local" immediately and the browser throws an error because it can't find that (how could it, there is no such thing).

[JonathanM]

Just to be clear, you are saying https://192.168.x.x/ redirects?

[alexfsr]

1 minute ago, jonathanm said:

Just to be clear, you are saying https://192.168.x.x/ redirects?

hmmm. Manually putting in the https in front makes it work. wtf??

https://192.168.x.x/  works

192.168.x.x/   redirects

[JonathanM]

1 minute ago, alexfsr said:

hmmm. Manually putting in the https in front makes it work. wtf??

https://192.168.x.x/  works

192.168.x.x/   redirects

http:// returns a redirect to the https://fqdn, which in your case doesn't work properly. https:// has no such redirect in place.

Disable the https and you should be back to normal.

[alexfsr]

2 minutes ago, jonathanm said:

http:// returns a redirect to the https://fqdn, which in your case doesn't work properly. https:// has no such redirect in place.

Disable the https and you should be back to normal.

I did. But i do want to use SSL but use self-signed cert and just have it redirect 192.168.x.x to https://192.168.x.x

[JonathanM]

SSL only works with FQDN, it can't be set up for an IP.