11 months ago

Mutliple domain and subdomains pointing to the same app

Posted 11 months ago by miadey

Hi :) I have an apps which use hyn/tenancy on Forge with Digital Ocean. This app is on a domain, neuroweb.ca and I have multiple tenancies on subdomain, sourire.neuroweb.ca. A client asked me to have there own domain, satisfaction.expert pointing to a wordpress site, and sourire.neuroweb.ca should now be sourire.satisfaction.expert. So I have cahnge there dns entry to have the www.satisfaction and satisfaction.expert pointing to there IP address and I added *.satisfaction.expert pointing to my server. I added an alias of satisfaction.expert to my neuroweb.ca app on Forge and it ping ok. Now, I already have an SSL for neuroweb and I'm trying to add an SSL to *.satisfaction.expert on Forge. I have tried many combination with no success. This is what I get when I add a LetsEncrypt SSL for *.satisfaction.expert and satisfaction.expert. Anyone bump into this kind of problem before ? Thank you

--2019-08-18 21:40:08-- https://forge-certificates.laravel.com/le/605800/713073?env=production Resolving forge-certificates.laravel.com (forge-certificates.laravel.com)...,, 2606:4700:20::6819:820, ... Connecting to forge-certificates.laravel.com (forge-certificates.laravel.com)||:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: letsencrypt_script1566164408

 0K ..                                                     32.9M=0s

2019-08-18 21:40:08 (32.9 MB/s) - letsencrypt_script1566164408 saved [2700]

Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator dns-digitalocean, Installer None Obtaining a new certificate Performing the following challenges: dns-01 challenge for satisfaction.expert dns-01 challenge for satisfaction.expert Unsafe permissions on credentials configuration file: letsencrypt/creds.ini Cleaning up challenges Encountered exception during recovery: Traceback (most recent call last): File "/usr/local/lib/python2.7/site-packages/certbot-0.31.0-py2.7.egg/certbot/error_handler.py", line 108, in _call_registered self.funcs-1 File "/usr/local/lib/python2.7/site-packages/certbot-0.31.0-py2.7.egg/certbot/auth_handler.py", line 323, in _cleanup_challenges self.auth.cleanup(achalls) File "/usr/local/lib/python2.7/site-packages/certbot-0.31.0-py2.7.egg/certbot/plugins/dns_common.py", line 76, in cleanup self._cleanup(domain, validation_domain_name, validation) File "build/bdist.linux-x86_64/egg/certbot_dns_digitalocean/dns_digitalocean.py", line 50, in _cleanup self._get_digitalocean_client().del_txt_record(domain, validation_name, validation) File "build/bdist.linux-x86_64/egg/certbot_dns_digitalocean/dns_digitalocean.py", line 116, in del_txt_record domain = self._find_domain(domain_name) File "build/bdist.linux-x86_64/egg/certbot_dns_digitalocean/dns_digitalocean.py", line 163, in _find_domain .format(domain_name, domain_name_guesses)) PluginError: Unable to determine base domain for satisfaction.expert using names: [u'satisfaction.expert', u'expert']. Unable to determine base domain for satisfaction.expert using names: [u'satisfaction.expert', u'expert']. cp: cannot stat '/etc/letsencrypt/live/certificate/privkey.pem': No such file or directory cp: cannot stat '/etc/letsencrypt/live/certificate/fullchain.pem': No such file or directory

Please sign in or create an account to participate in this conversation.