Hello everyone!
I am not sure if this is a Truenas problem, or DNS problem, or a nextcloud problem, but at this point I am loosing my mind.
I set up a fresh install of nextcloud. Everything works fine.
I opened up port 443 on my router and froward it to port 9001 on my truenas, which is the nextcloud instance.
I bought an SSL certificate from ionos. I imported the certificate into Truenas, and set the certificate to nextcloud.
Then I created a subdomain, and created an A record for this subdomain which points to my public IP.
And here comes the part, which I don't understand.
I have my domain example.com.
If I open subdomain.example.com, then it will try to open my internal IP (192.168.x.x), which is obviously not working. I can see that the address bar of the browser actually tries to open https://192.168.x.x:9001/login
If however, I open subdomain.example.com/login then everything is working fine.
Could someone please help me to solve this? I don't think that by opening subdomain.example.com my internal IP should be visible. Also I don't understand why I have to write /login after subdomain.example.com so it works? If I simply open https://mypublicIP then it will get automatically redirected to the /login page.
Thanks in advance!
I am not sure if this is a Truenas problem, or DNS problem, or a nextcloud problem, but at this point I am loosing my mind.
I set up a fresh install of nextcloud. Everything works fine.
I opened up port 443 on my router and froward it to port 9001 on my truenas, which is the nextcloud instance.
I bought an SSL certificate from ionos. I imported the certificate into Truenas, and set the certificate to nextcloud.
Then I created a subdomain, and created an A record for this subdomain which points to my public IP.
And here comes the part, which I don't understand.
I have my domain example.com.
If I open subdomain.example.com, then it will try to open my internal IP (192.168.x.x), which is obviously not working. I can see that the address bar of the browser actually tries to open https://192.168.x.x:9001/login
If however, I open subdomain.example.com/login then everything is working fine.
Could someone please help me to solve this? I don't think that by opening subdomain.example.com my internal IP should be visible. Also I don't understand why I have to write /login after subdomain.example.com so it works? If I simply open https://mypublicIP then it will get automatically redirected to the /login page.
Thanks in advance!