Hello guys, I’m having a hard time trying to setup my own domain on yunohost.
I’ve followed all the instructions from the dns_config page and the admin’s page for mydomain recommend configuration to set namecheap’s dns to my yunohost’s services. After that ‘https://www.mydomain.net’ now takes me to yunohost’s admin, but without ‘www’ part it takes me nowhere and after installing nextcloud app, I am not able to access it anywhere, which should be on ‘https://mydomain.net/nextcloud’ and putting the ‘www’ part would take me again to yunohost’s admin page.
If you want to be able to access your server on that address, yes. Otherwise, the server (nginx) acts as it does not know this domain (even though it knows yourdomain.tld)
Keep in mind that for YunoHost, there’s no concept of domain and subdomains, for “domain.tld” and “www.domain.tld” are just like two different domains with no relationship. So if you install nextcloud on domain.tld, it won’t be available via www.domain.tld anyway. Though you can setup a redirection from www.domain.tld to domain.tld …
In terms of DNS setup, I don’t think you have anything more to do apart from adding a A record for www or * (wildcard) poiting to your IP adress. This is among the stuff recommended in the doc so maybe you already did it
Regarding your nextcloud not being accessible, that’s probably a different issue, but let’s already confirm that we understand the www thing
As I mentioned I did this [1] for mydomain.net (without ‘www’) on Namecheap. So you say I should add www.mydomain.net on yunohost’s admin interface only? I should not do anything on namecheap’s side for now right?
OK I managed to get nextcloud working. I just needed to add a new domain on yunohost (cloud.mydomain.net) and install on it.
I was not sure I should be adding this subdomains (www, cloud, etc) via yunohost interface, that’s were I missed the point.
Thanks for showing me the right directions.
Feel free to add additional comments for improving my actual DNS clueless state i live in :).
now for emails, I can get a working email service configuring the address ‘email@cloud.mydomain.net’ but can’t for ‘email@mydomain.net’ which is what I really want…When sending an email to this address I get this error:
DNS Error: 5990009 DNS type ‘mx’ lookup of mydomain.net responded with code NXDOMAIN Domain name not found: mydomain.net
OK, i managed to solve it. This was due to a configuration problem on namecheap. CNAME records were inverted host-value and for hostname instead of @ had to put mydomain.net because for them @ only works in a host field.
Hello Aleprovencio! I’m trying to configure YunoHost using a NameCheap domain, and I see you managed. Perhaps you could help me a bit? I have set the recommended DNS records, but when I try to generate the Let’s Encrypt certificate, I get “Exception: [Errno 22] Signing the new certificate failed”.
Good eye, Aleks. I cannot access from outside the local network, and I thought that this was due to the certificate error. This is what I have tried:
port-forwarding rules don’t open ports 80 nor 443 (ISP most likely blocks them)
in my home router, placing the server on the DMZ opens all ports except 80 and 443
in the server, I opened 8080 and 4433
in the server, I replaced 80 and 443 with 8080 and 4433 in my.domain.conf
in the DNS records, I created a redirect URL record to mydomain:8080
in the server, in /etc/hosts/, I have tried replacing the 127.0.0.1 or 127.0.1.1 values with my.domain, as suggested here
I am also aware that changing 443 for another value can be a problem, as suggested here
In sum: ISP blocks ports 80 and 443, I have failed at opening or changing these ports, cannot access the server from outside the local network. I found threads about how to use different ports, such as this, but have had no luck. Any advice or documentation on how to handle this “port 80 blocked” problem would be largely appreciated!
Hmmm well if your ISP blocks 80 and 443, I would say you should use a VPN… Trying to change the port is not a good idea, you don’t want to have to tell your visitors that they should go to domain.tld:8080 instead of just domain.tld (though that might depend on the purpose of your server)
