Domains outside cloudron
-
Hello,
I have this problem I installed cloudron and it is now blocking all my domains (IP address).
I have several VPS, but only one public IP address and I need to somehow set cloudron to only pay attention to the domains on the VPS it is running on or only the domains it has added in the settings and leave all other VPS/domains alone.
Specifically, the following message is displayed:
You are seeing this page because the DNS record of xxxxx.yy is set to this server's IP but Cloudron has no app configured for this domain.
Is there any way to set this up please? Thanks in advance for the advice.
-
@1Psychedelic You know, I think I sort of understand your question... but then nothing about it makes sense!
Check out https://docs.cloudron.io/domains/#wildcard-dns which gets more into details about how to connect domains to your Cloudron using A records and IP numbers. Basically, you need to point the domains you want to be used by Cloudrdon to the VPS by making A records in the domain registrar using the IP number of the VPS.
If none of what I said makes sense, I suggest reading the documentation over alot. This stuff gets clearer. I've found that when I ask technical questions without using (or knowing) the correct technical terms in a forum like this (but not this one... this one is awesome), it's difficult for others to know what I'm getting at. So, I google the phrase I have in mind ("point my domain to my VPS, how?") and read most of the first page of results. It will either click, and you'll get it, or you'll be better prepared to ask the question you need an answer to. Good luck!
-
It kind of sounds like then classic "i am running my cloudron on my server at home" scenario. Cloudron recently gained a functionality to act as a reverse proxy for other services. This could be used to connect your other services.
The question is: how did you expose your other servers before and is there a way to include cloudron in this configuration.
-
I'm sorry, my English is not very good, so I understand that you don't understand me...
I know how to set up DNS, I use a reverse proxy, but my problem is elsewhere...
I have added aaaa.com and bbbb.com domain in cloudron, cloudron is running on VPS-A and both domains have one public IP address for example 172.22.0.160.
Then I have another VPS-B, on this VPS I have the domains cccc.com, dddd.com, eeee.com, gggg.com... Again they all have one public IP 172.22.0.160, only they run on different ports and none of the domains on VPS II are added in cloudron.
However, when I open the eeee.com domain that runs on VPS-B, I get an error from cloudron:
You are seeing this page because the DNS record of eeee.com is set to this server's IP but Cloudron has no app configured for this domain.
So after installing cloudron all my projects on all VPS are down, even though they have nothing to do with cloudron. I can only get to the web if I specify the domain and port (eeee.com:8444).
Sorry again, hopefully it's more understandable now..
-
@1Psychedelic No really, but that was a good explanation. @fbartels suggested you are on a home server... are you? Is each VPS really a VM on a computer? I myself run different VMs on my laptop and run into the issue of conflicting ports - I have to shut down one VM, running Wordpress, so that the other VM running something else can work. Sometimes on my VPS running LAMP I have to stop Apache so that certbot can run (it wants to use port 80 which is what Apache uses).
In the end, Cloudron has to be the only thing running.
Here is another link about using it on a homeserver, which it sounds like you are: https://blog.cloudron.io/installing-cloudron-on-a-home-server/
-
@1Psychedelic said in Domains outside cloudron:
I know how to set up DNS, I use a reverse proxy, but my problem is elsewhere...
So, Cloudron is behind a reverse proxy ? The issue is that requests to
cccc.com
are ending up to Cloudron VPS . This seems like a reverse proxy misconfiguration . You have to configure the reverse proxy to makecccc.com
go to VPS-B . -
I already solved it, I simply added a new domain.conf file with the following content to the VPS-A running cloudron:
server { server_name cccc.com; location / { proxy_pass VPS-B_IP:5678; proxy_set_header Host $host; proxy_redirect http:// https://; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $connection_upgrade; } listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/cccc.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/cccc.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot } server { if ($host = cccc.com) { return 301 https://$host$request_uri; } # managed by Certbot server_name cccc.com; listen 80; return 404; # managed by Certbot }
-
@1Psychedelic instead of adding it manually, use https://docs.cloudron.io/apps/#app-proxy . This will prevent it getting overwritten during updates .
-
-