still violet
Add the following to the additional hosts of Cloudflared.
service: http://hostname:9999```
You have to change hostname to the Nextcloud add-on's hostname (can be found on the main page of the running add-on) and the port number according to the exposed one.
pure sleet
Let me test
pure sleet
Add the following to the additional hosts of Cloudflared.
```- hostname: cloud.m...
Nothing is happening unfortunately, the strange thing is that I cannot even reach home.mydomain.com:8099 to see the web ui, only localhost:8099
still violet
The Cloudflared URL has no custom ports. It is always 443.
The home subdomain is forwarded to the HA instance, the cloud one to Nextcloud.
You can check in the Cloudflare DNS web portal, if the DNS entries have been created. And it might need some time for them to propagate.
pure sleet
@still violet I continue receivng a bad gateway error, at least this time reported by Cloudflare
direct public IP:8099 is working
I opened the port on my router for testing purposes in case cloudflared doesn't work
still violet
That is wrong. The hostname has to be the one of Nextcloud and its port.
still violet
Is it a valid https connection? I guess it should be http
pure sleet
let me give it another shot
still violet
Meaning with a trusted SSL certificate.
pure sleet
Which CURL can I paste in terminal to see
I changed to http and still gateway error
still violet
Then try the IP number you use for direct access.
pure sleet
Internal or external?
Alright
It works!!
That did the trick
external_hostname: home.xxx.com
additional_hosts: