Hi
I would like to use several services like AdGuard, ownCloud, … on one DietPI.
My Asus router has a DDNS service and routes the domain: sampledomain.asuscomm.com to my fixed IP.
I would like the above-mentioned domain to direct only MQTT or Node-Red type connections.
I understand that it needs other domains configured in some way to make http/s:// work on other ports
I could use a no-ip service, or buy some domains (do you know of any cheap ones that can be bought for life?).
How do I bundle it all up so it works without a problem?
In no-ip, specify sampledomain.asuscomm.com:81 and have ownCloud listen on another port? What about https?
To setup HTTPS you can just use dietpi-letsencrypt when you already have a DDNS or another domain.
You could also forward other ports in your router for example for adguard, which uses 8083.
Or you use a reverse proxy (which can be difficult to set up) to “route” the request to a domain like sampledomain.asuscomm.com/adguard or sampledomain.asuscomm.com/owncloud instead of using domain:port.
sampledomain.no-ip.biz I’ll for ownCloud for now. But how I can setup ownCloud for listening on port 2080 and 2443? Or only 2443 for https only?
I can forward port and set no-ip for sampledomain.no-ip.biz → sampledomain.asuscomm.com:2443 ??
It doesn’t matter how much DDNS domain you have. They all will resolve to the very same external IP address. Therefore, you can’t use port 443 more than once. As it is blocked by AGH, it can’t be used by OwnCloud to do HTTPS/SSL
The only solution to reach AGH + Ownlcoud on port 443, would be to setup a revers proxy. This would be the most elegant solution as the proxy would handl all SSL certificates and you don’t need to configure each and every app to do HTTPS individually.
as stated above, this doesn’t matter how much domains you will use. At the end a port can be used once. For using it multiple time, a proxy is needed who could decide, depending on your domain, what to do. And Nginx is quite a good option to setup the proxy. However, you would need to remove port 443 on AGH + disable SSL, create a cert for Nginx using dietpi-letsencrypt. Once this is working and Owncloud is reachable on HTTPS, you could create the proxy entry for AGH.
what should be the goal of this? Are there clients/devices that should connect to AGH using DoT? Or should AGH connect to upstream DNS using DoT? Maybe try to describe the solution a little more on what you are trying to achieve.
HTTPS port is 443.
8083 is the HTTP port of AGH. SSL is done by Nginx now and not by AGH anymore.
It would require a complete rework on the Nginx configuration, if you like Nginx to decide by domain what to do. You need to create VirtualHost entries per domain and block access by IP.