ucrbuffalo

So I shouldn't do incremental updates to keep all my plugins up to date along the way? Is that not more likely to break the ones I've got?

I went through a divorce a few years ago and had to shut down the server for a while. Now that I've got it back up and running, I'm trying to update the OS, but some of the plugins I've got can't update because they need at least 6.9 to run. How can I make incremental updates to the OS, instead of jumping straight to the latest release?

Yes. I manually checked my public IP address and it matches correctly.

I'm hoping someone here can help me out. I'm really starting to run out of any ideas to figure this out... Lets get this out of the way first... Here are screenshots of my DuckDNS Docker Settings, LetsEncrypt Docker settings, and Router Port Forwarding settings. Additionally, here is what my default file in the site-conf directory looks like. I can't seem to get this working at all. When I attempt to connect to the site, I get an error that says that the page cannot be reached. It doesn't appear that NGINX is even running though. I have tried everything I can think of at this point and I'm just at a total loss... When I run "ps aux | grep nginx", here's what I get: 333 root 0:00 grep nginx And the Log doesn't seem to help me much either, other than to say there may be some sort of firewall issue, but I don't see anything wrong as of yet: [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] 30-keygen: executing... using keys found in /config/keys [cont-init.d] 30-keygen: exited 0. [cont-init.d] 50-config: executing... Variables set: PUID=99 PGID=100 TZ=America/Chicago URL=duckdns.org SUBDOMAINS=XXXXXXXXXX EXTRA_DOMAINS= ONLY_SUBDOMAINS=true DHLEVEL=2048 VALIDATION=http DNSPLUGIN= [email protected] STAGING= Backwards compatibility check. . . No compatibility action needed 2048 bit DH parameters present SUBDOMAINS entered, processing SUBDOMAINS entered, processing Only subdomains, no URL in cert Sub-domains processed are: -d XXXXXXXXXX.duckdns.org E-mail address entered: [email protected] http validation is selected Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for XXXXXXXXXX.duckdns.org Waiting for verification... Cleaning up challenges Failed authorization procedure. XXXXXXXXXX.duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://XXXXXXXXXX.duckdns.org/.well-known/acme-challenge/f1rdD3LNSvZDXNlOZy15GcVFK4LOQqvIZ_KyXSXpJFw: Timeout during connect (likely firewall problem) IMPORTANT NOTES: - The following errors were reported by the server: Domain: XXXXXXXXXX.duckdns.org Type: connection Detail: Fetching http://XXXXXXXXXX.duckdns.org/.well-known/acme-challenge/f1rdD3LNSvZDXNlOZy15GcVFK4LOQqvIZ_KyXSXpJFw: Timeout during connect (likely firewall problem) To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container Please tell me there's someone that can help... I don't have much hair left to pull. Thanks in advance.