Hardware: Old laptop or computer YunoHost version: started when using 3.6.4.6 but since updated to 3.7.0.12 problem persists. I have access to my server: Through webadmin.
Are you in a special context or did you perform some particular tweaking on your YunoHost instance?: no
Description of my issue
My Yunohost is no longer accessible outside of my network (but browsers and internet are).
When I use the YunoHost port tester all appear red, however when I check my router and firewall settings the ports are open.
I havenāt figured this out and my instance has been in limbo since itās a non-critical, family/testing at this point only. However recently I started receiving emails about the "Certificate renewing attempt for my.domain failed!"
Which gave me this clue
"YunohostError: It seems the domain my.domain cannot be accessed through HTTP. Check that your DNS and NGINX configuration is correct"
Basically make sure that you followed https://yunohost.org/isp_box_config (though you seem to say that you already configured port stuff ā¦)
Also check that you registered a DNS record on your DNS provider ?
Otherwise, this warning could be a false-negative and you can try to run from the command line "sudo yunohost domain cert-install yourdomain.tld --no-checks"
Iām confused since this was working using the YunoHost provided subdomain and then one day just stopped, so I donāt thing DNS is an issue if Iām using the Subdomain is it?
Iāll try the command to see what I come up with and look at the isp_box_config. I checked my ports using https://ports.yunohost.org/
And again, this was working until a few weeks ago.
I donāt think so, Iām just grasping at anything as I canāt figure out what happened. This occurred before the expiry of certificates.
Iāve been considering just doing a fresh install on another drive and hoping to use the same subdomain, and restoring with a YunoHost backup. Is this possible?
Just ā¦ give the result of the command (ideally redacting private info like domain name if you care about privacy)
Please no, itās like moving to a new flat because your microwave doesnāt work ā¦ Given the nature of the issue itās not likely to solve anything, youāll just waste your time ā¦ We just need to precisely diagnose the issue and apply the appropriate fix.
I recommand you to follow @Aleks suggestion to check your certificate.
If the command returns that your certificate is a valide LetāsEncrypt certificate, may be your isp share now your IP address with other customer OR change the settings of your box.
If your IP is shared you could need to ask your ISP for a āfull stack ipā.
Error: Certificate renewing for my.domain failed !
Info: The operation āRenew āmy.domainā Letās Encrypt certificateā could not be completed. Please share the full log of this operation using the command āyunohost log display 20200331-234226-letsencrypt_cert_renew-my.domain --shareā to get help
Error: Traceback (most recent call last):
File ā/usr/lib/moulinette/yunohost/certificate.pyā, line 384, in certificate_renew
_fetch_and_enable_new_certificate(domain, staging, no_checks=no_checks)
File ā/usr/lib/moulinette/yunohost/certificate.pyā, line 577, in _fetch_and_enable_new_certificate
raise YunohostError(ācertmanager_cert_signing_failedā)
YunohostError: Could not sign the new certificate
Alright so i confirm that I also cannot access your ip over http/https, so that definitely looks like an issue about port forwarding ā¦ I understand that it was working a few days or weeks ago and that you probably dindāt touch anything, but you have to forget about this myth that ācomputers things work foreverā. In reality, they do have many stupid reasons to spontaneously break from one day to the nextā¦ (Fortunately we will have regular automatic diagnosis shipped in YunoHost 3.8 to help make it easier and faster to spot this and pinpoint the actual issueā¦)
Anyway, I can just advise you to carefully read https://yunohost.org/isp_box_config and make sure that your port forwarding configuration is correct on your router / internet box interface ā¦
If that still isnt the issue, then I do agree with ljf about investigating the fact that your ISP might have decided that you canāt control port 80/443 anymore and/or maybe you now have an IP shared with other customer. But first letās do the usual check on your router interfaceā¦
Iāve gone through the docs in the first place but will go over them again. I really hope I donāt need to deal with my ISP about this, thatāll be a headache.
Unrelated to this but I thought Iād ask anyway. Since I upgraded to Nextcloud 18 it went directly to Maintenance Mode. How do I get out of it? Itās been over a day.
On the other hand, I can tell that ports.yunohost.org is not always reliable ā¦ But if you have a linux machine that is preferrably not on the same local network, you can make sure of this by running nc -w 3 your.ip 22 (for example to check port 22)
For anyone following this thread I wanted to say I resolved my issue and @Aleks was correct. It had to do with my port forwarding. I discovered that the automatically assigned IP address for my device/server had changed from what I had in my āVirtual Servers/Port Forwardingā dialogue on my router.
For example I had forwarded the ports for ā192.168.0.108ā which my machine had automatically been assigned and after a power outage the router simply assigned another number ā192.168.0.142ā but I didnāt change me port forwarding rules.
Now Iām off to read the router docs on how to hold a specific IP address so this doesnāt happen again.