SSL cert not updating #400

tactmaster · 2023-02-08T07:08:24Z

Problem/Motivation

SSL Certs not getting update from lets encrypt

Expected behavior

Lets encrypt ssl cert being automatically updated

Actual behavior

ssl certs not being updated. Is you press renew get this error

Steps to reproduce

Proposed changes

SoulOfNoob · 2023-02-08T16:42:13Z

I had the same issue today.
It turned out, that my Pi got a new IP address and my port forwarding pointed to the wrong one.

I had to login to the Pi via SSH and open "/data/logs/letsencrypt/letsencrypt.log" inside the proxymanager docker container to find the exact issue was:

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

tactmaster · 2023-02-08T20:19:28Z

This error I got

Some of certs are renewing some are not it is odd

  Command: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-2" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation 
[08/Feb/2023:21:15:18 +0100] - 200 200 - GET https aaa.bbb.com "/api/config" [Client 10.0.0.153] [Length 6152] [Gzip -] [Sent-to 192.168.1.75] "-" "-"
[2/8/2023] [9:15:19 PM] [Express  ] › ⚠  warning   Command failed: certbot renew --force-renewal --config "/etc/letsencrypt.ini" --cert-name "npm-2" --preferred-challenges "dns,http" --no-random-sleep-on-renew --disable-hook-validation 
Another instance of Certbot is already running.

tactmaster · 2023-02-15T20:03:48Z

Things I tried.
Resetting the database
Uninstalling and restoring from backup.

Deleting the certificate and asking for it again from the UI worked

eric10k93 · 2023-03-07T08:47:18Z

I'm getting the same "Internal Error" simply when trying to create a brand new SSL cert. I was also getting the error "Another instance of Certbot is already running". I just rebooted my system to get it to shut down all processes... as obviously there was a stuck Certbot instance. After a restart, I wasn't getting the same error... Now I am just getting "Some challenges have failed" from Let's Encrypt and it's unable to generate a new certificate for me. I'm at a loss. If I use Let's Encrypt via the DuckDNS add on, it generates the SSL certs for me just fine and I am then able to reference them via NPM by adding them as "Custom" SSL certs. This works, but it's obviously not ideal because I then have to manually renew the certs anytime they come up for renewal.

awdark · 2023-03-23T22:11:03Z

DuckDNS add on, it generates the SSL certs for me just fine and I am then able to reference them via NPM by adding them as "Custom" SSL certs. This works, but it's obviously not ideal because I then have to manually renew the certs anytime they come up for renewal.

Would you mind sharing your process? I have the DuckDNS add on but I don't know where it stores the certs so I can add them as custom. My cert expired and I want to keep it going until it hopefully gets patched.

I may be digging myself into a bigger hole tried to add homeassistant.something.duckdns.org
ended up with ["error"] {"type":"urn:ietf:params:acme:error:unauthorized","detail":"Incorrect TXT record "dns-01" found at _acme-challenge.homeassistant.something.duckdns.org","status":403}

I noticed in duckdns documentation the folder \ssl\ is supposed to contain the certificates but they are dated December and I tried to just install those anyways and got an error about using those certificates so I don't think those are the right ones.

EDIT
Problem in chair.
Still not 100% sure what fixed it, but I opened up my firewall and reverted the port number for port 80 to port 80.

TerrorBite · 2023-04-09T17:38:07Z

Also experiencing this issue.

Addon Version: 0.12.3

Upon attempting to create or renew a cert:

[4/10/2023] [3:23:18 AM] [SSL      ] › ℹ  info      Testing http challenge for DOMAIN.REDACTED
Uncaught SyntaxError: Unexpected end of JSON input
FROM
2023/04/10 03:23:19 [error] 298#298: *3 upstream prematurely closed connection while reading response header from upstream, client: 10.10.0.4, server: nginxproxymanager, request: "GET /api/nginx/certificates/test-http?domains=%5B%22DOMAIN.REDACTED%22%5D HTTP/1.1", upstream: "http://127.0.0.1:3000/nginx/certificates/test-http?domains=%5B%22DOMAIN.REDACTED%22%5D", host: "10.10.0.200:81", referrer: "http://10.10.0.200:81/nginx/certificates"
[03:23:20] INFO: Nginx Proxy Manager stopped, restarting...
[03:23:20] INFO: Starting the Manager...

Following this crash and restart…

[4/10/2023] [3:23:34 AM] [Nginx    ] › ℹ  info      Reloading Nginx
[4/10/2023] [3:23:39 AM] [SSL      ] › ℹ  info      Requesting Let'sEncrypt certificates for Cert #2: DOMAIN.REDACTED
[4/10/2023] [3:23:39 AM] [SSL      ] › ℹ  info      Command: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-2" --agree-tos --authenticator webroot --email "EMAIL@REDACTED" --preferred-challenges "dns,http" --domains "DOMAIN.REDACTED" 
[4/10/2023] [3:23:44 AM] [Nginx    ] › ℹ  info      Reloading Nginx
[4/10/2023] [3:23:44 AM] [Express  ] › ⚠  warning   Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-2" --agree-tos --authenticator webroot --email "EMAIL@REDACTED" --preferred-challenges "dns,http" --domains "DOMAIN.REDACTED" 
Another instance of Certbot is already running.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-j7u3fnai/log or re-run Certbot with -v for more details.
[4/10/2023] [3:24:05 AM] [SSL      ] › ✖  error     Error: Command failed: certbot renew --non-interactive --quiet --config "/etc/letsencrypt.ini" --preferred-challenges "dns,http" --disable-hook-validation  
Failed to renew certificate npm-1 with error: Some challenges have failed.
All renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/npm-1/fullchain.pem (failure)
1 renew failure(s), 0 parse failure(s)
    at ChildProcess.exithandler (node:child_process:400:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1093:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)

After this point all attempted Let's Encrypt operations continue to fail.

github-actions · 2023-05-10T08:15:25Z

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

ghost · 2023-05-16T16:26:39Z

It is still a problem.

fgibaux · 2023-06-02T20:23:28Z

I believe that's more of an upstream issue, cf NginxProxyManager/nginx-proxy-manager#2881

github-actions · 2023-07-03T08:17:37Z

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

SiriosDev · 2023-07-03T23:31:40Z

Absolutely not stale

awdark · 2023-07-04T02:56:51Z

Do you run a firewall?
It seems like some zone protection or other filters may block these requests. Strangely they didn't show up on the logs as far as I could tell but running with everything on alert made it work smoothly.

Scags104 · 2023-07-24T15:11:26Z

Same issue here but deleting, trying to reissue causes more problems. I should have let them expire on their own, lost a month now...

Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-12" --agree-tos --authenticator webroot --email "[email protected]" --preferred-challenges "dns,http" --domains "rondemealie.duckdns.org" 
Another instance of Certbot is already running.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /tmp/certbot-log-kuhouk5g/log or re-run Certbot with -v for more details.

    at ChildProcess.exithandler (node:child_process:400:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1093:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)

github-actions · 2023-08-24T08:14:27Z

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

Scags104 · 2023-08-24T10:27:22Z

Still a problem

geigervlad · 2023-08-27T18:16:57Z

just had the same issue. For me the issue was misconfiguration under router: port 80 was not forwarded/open.

Certmanager uses Port 80 to execute the HTTP check. Make sure it is open and forwarding to the correct machine

SiriosDev · 2023-08-27T18:28:16Z

just had the same issue. For me the issue was misconfiguration under router: port 80 was not forwarded/open.

Certmanager uses Port 80 to execute the HTTP check. Make sure it is open and forwarding to the correct machine

this issue talks about problems when enabling forcing on https, the problem is that http verification is also being forced on 443 sending the whole thing into error

github-actions · 2023-09-27T08:16:04Z

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

Scags104 · 2023-09-27T12:45:56Z

still an issue

sulazix · 2023-09-29T06:11:51Z

I have the same issue

eric10k93 · 2023-10-04T20:01:34Z

I feel kinda dumb coming back to this after all this time having issues... but I think I figured out my problem... I've been using this with a DuckDNS domain and it appears it needs a DNS challenge... the DuckDNS addon for HA handles the challenge with the supplied token, which is why I never saw any issues with that addon getting a valid cert. Basically, the problem boils down to there being poor documentation for both the DuckDNS addon and this NPM addon. It was never clear to me that I NEEDED to do the DNS challenge... but it seems obvious now. Basically, I stopped using the DuckDNS addon... I no longer use a custom cert in NPM. Just have NPM create and manage the certs and use the appropriate DNS challenge for your DDNS provider. This appears to be working fine for me this way. Time will tell if the certs update properly when needed, but they should now that they have the appropriate token.

Scags104 · 2023-10-05T13:21:11Z

I feel kinda dumb coming back to this after all this time having issues... but I think I figured out my problem... I've been using this with a DuckDNS domain and it appears it needs a DNS challenge... the DuckDNS addon for HA handles the challenge with the supplied token, which is why I never saw any issues with that addon getting a valid cert. Basically, the problem boils down to there being poor documentation for both the DuckDNS addon and this NPM addon. It was never clear to me that I NEEDED to do the DNS challenge... but it seems obvious now. Basically, I stopped using the DuckDNS addon... I no longer use a custom cert in NPM. Just have NPM create and manage the certs and use the appropriate DNS challenge for your DDNS provider. This appears to be working fine for me this way. Time will tell if the certs update properly when needed, but they should now that they have the appropriate token.

I just tried this. Disdabled DuckDNS, NPM began working when forcing a challenge and using my DuckDNS token
All seems to be ok for the moment!

Thanks for this

github-actions · 2024-01-05T08:16:02Z

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

tactmaster · 2024-01-05T08:20:01Z

Doesn't seem to be fixed The best work around i have found is just to delete the ssl certificate and re created it.

…

On Fri, 5 Jan 2024, 08:16 github-actions[bot], ***@***.***> wrote: There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks! — Reply to this email directly, view it on GitHub <#400 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGBUHPMBUINLT2OIXBY3JLYM6ZEZAVCNFSM6AAAAAAUU4EQB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZYGI4DMMBZGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

mathwizmf2009 · 2024-01-05T13:50:29Z

Yeah, my certs failed to renew this month. Not sure why, I'm hoping to dig into it more today. Hitting the button to manually renew worked on 2 of them, but not on my 3rd.

kaffeepause07 · 2024-01-05T14:29:48Z

Do you use the "Force SSL" option in the ssl settings?
This was the cause in my homelab, i was able to fix it with a workaround. (custom force-ssl.conf)
For testing you can disable "Force SSL" temporary.

akrigator · 2024-01-05T16:56:13Z

I have faced with same issue: can create a certificate, but it fails to renew after 2 months, with error like: Failed to renew certificate npm-2 with error: The DNS response does not contain an answer to the question
In my case issue was in the local DNS setup. It has a special cname record for resolve services by NPM domain names in LAN, which uses the ^(.*\.)?mydomain\.duckdns\.org$ regex. The regex picks requests to mydomain.duckdns.org and *.mydomain.duckdns.org wildcard, but Let's Encrypt uses the _acme-challenge.mydomain.duckdns.org to verify domain owner by placing a token to TXT record. Let's Encrypt sends a request from LAN during certificate renewal process, the request goes to the local DNS where TXT record does not have the token to validate owner, since TXT is updated on DuckDNS.
So the fix for me was to exclude the _acme-challenge subdomain from resolving scope of local DNS:
^(?!_acme-challenge)(.*\.)?mydomain\.duckdns\.org$

mathwizmf2009 · 2024-01-05T20:06:33Z

I have faced with same issue: can create a certificate, but it fails to renew after 2 months, with error like: Failed to renew certificate npm-2 with error: The DNS response does not contain an answer to the question In my case issue was in the local DNS setup. It has a special cname record for resolve services by NPM domain names in LAN, which uses the ^(.*\.)?mydomain\.duckdns\.org$ regex. The regex picks requests to mydomain.duckdns.org and *.mydomain.duckdns.org wildcard, but Let's Encrypt uses the _acme-challenge.mydomain.duckdns.org to verify domain owner by placing a token to TXT record. Let's Encrypt sends a request from LAN during certificate renewal process, the request goes to the local DNS where TXT record does not have the token to validate owner, since TXT is updated on DuckDNS. So the fix for me was to exclude the _acme-challenge subdomain from resolving scope of local DNS: ^(?!_acme-challenge)(.*\.)?mydomain\.duckdns\.org$

This is interesting. This seems to have been related to my issue, but I'm not 100% sure how to fix it properly. My DNS rewrite only handles mysub.mydomain.duckdns.org (rather than *.mysub.mydomain.duckdns.org). I have a separate rewrite for mydomain.duckdns.org. My AdGuard Home addon is handling my DNS rewrites. I could see the DNS requests for mysub.mydomain.duckdns.org (no reference to _acme-challenge listed, but clearly labeled as a TXT request). I deleted the mysub.mydomain.duckdns.org rewrite just to test and manually refreshed the cert (which worked).

The more interesting thing is that my cert for mydomain.duckdns.org was able to manually refresh even with its rewrite still in place. All doing the DNS-01 challenge. But I don't even see the mydomain.duckdns.org TXT DNS request in the AdGuard logs.

When I test a ping to <something>.mysub.mydomain.duckdns.org, it doesn't route to my LAN, but rather to my public IP. I also see that specific request, including <something> within AdGuard. It isn't referencing an _acme-challenge sub-sub(?) domain within the AdGuard logs during renewal, and if it did then it shouldn't be routed to my LAN anyway based on my ping testing. Maybe I can change the Type of requests that are rewritten? I'm inexperienced with the custom filtering rules, so it looks like I'll need to do a bit more research into that side of things. Maybe I'm implementing my DNS rewrites poorly, or maybe I'm making totally incorrect assumptions based on my ping testing due to it being a different type of DNS request?

akrigator · 2024-01-05T20:56:55Z

This is interesting. This seems to have been related to my issue, but I'm not 100% sure how to fix it properly. My DNS rewrite only handles mysub.mydomain.duckdns.org (rather than *.mysub.mydomain.duckdns.org). I have a separate rewrite for mydomain.duckdns.org. My AdGuard Home addon is handling my DNS rewrites. I could see the DNS requests for mysub.mydomain.duckdns.org (no reference to _acme-challenge listed, but clearly labeled as a TXT request). I deleted the mysub.mydomain.duckdns.org rewrite just to test and manually refreshed the cert (which worked).

The more interesting thing is that my cert for mydomain.duckdns.org was able to manually refresh even with its rewrite still in place. All doing the DNS-01 challenge. But I don't even see the mydomain.duckdns.org TXT DNS request in the AdGuard logs.

Here a lot of things to check:

Make sure that there is no another DNS in use. In my router got 2 additional DNS from ISP which were propagated to all DHCP clients. In result: requests were balanced between AdGuard and ISP DNSs
Flush DNS cache in AdGuard after updating rules
Flush DNS cache in router if it is used as proxy for AdGuard

When I test a ping to <something>.mysub.mydomain.duckdns.org, it doesn't route to my LAN, but rather to my public IP. I also see that specific request, including <something> within AdGuard. It isn't referencing an _acme-challenge sub-sub(?) domain within the AdGuard logs during renewal, and if it did then it shouldn't be routed to my LAN anyway based on my ping testing. Maybe I can change the Type of requests that are rewritten? I'm inexperienced with the custom filtering rules, so it looks like I'll need to do a bit more research into that side of things. Maybe I'm implementing my DNS rewrites poorly, or maybe I'm making totally incorrect assumptions based on my ping testing due to it being a different type of DNS request?

Try to monitor dig mydomain.duckdns.org TXT from lan and internet during renewal.
And as I know renewal in NPM will actually renew certificate only if it older then 2 month, unfortunately i don't know how to force it.

github-actions · 2024-02-05T08:15:49Z

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

SiriosDev · 2024-02-05T12:03:27Z

mope

mathwizmf2009 · 2024-02-16T17:12:41Z

For anyone else using AdGuard Home alongside their NPM and having issues with renewing their SSL certs, it might be that your AdGuard Home is doing a DNS rewrite of your TXT requests. You may be able to see this within your AdGuard logs. For me, I didn't see the _acme-challenge subdomain within the logs, but I DID see the Type: TXT. More on DNS-01 challenges

To solve this, I needed to remove the DNS rewrite from the Filters->DNS rewrites section and make a custom rule (Filters->Custom filtering rules). The Syntax for this is a bit annoying if you aren't used to it (like me), but after some trial and error plus reading the docs, I was able to come up with a rule to work for me that I couldn't find elsewhere:

|example.com^$dnsrewrite=1.2.3.4,dnstype=A|CNAME|AAAA

I didn't want to rewrite all subdomains, so the single pipe at the beginning | resolves this. If you want to include all subdomains, I believe you can use a double-pipe ||. I tried following the docs where it says |example.com^$dnsrewrite=NOERROR;A;1.2.3.4 adds an A record with the value 1.2.3.4, thinking it would only rewrite A records, but this wasn't the case and it rewrote all other types to NOERROR. The dnstype Rule Modifier appended on the end did work though!

Since I just upgraded my NPM add-on and applied these rules, I don't know yet if I'll have issues when my certs try to auto-renew in a couple months. Hopefully the combination of the add-on update and fixing my local DNS finally resolves this for me.

github-actions · 2024-04-14T10:35:39Z

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

tactmaster · 2024-04-14T10:38:39Z

This is still an issues with latest release. I think the next step is get in the docker imagine an try it myself. To see the exact error

…

On Sun, 14 Apr 2024, 12:35 github-actions[bot], ***@***.***> wrote: There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks! — Reply to this email directly, view it on GitHub <#400 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGBUHILDEYKASF5Y7EWHLDY5JLY7AVCNFSM6AAAAAAUU4EQB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJUGAYDEMJUGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Blogshot · 2024-04-14T16:32:44Z

I believe that's more of an upstream issue, cf NginxProxyManager/nginx-proxy-manager#2881

Yes, it is. The reason is that the "Force SSL" option will redirect the HTTP challenges to HTTPS, which the integrated certbot doesnt support apparently. A pull request is open at NginxProxyManager/nginx-proxy-manager#3121, but the fix hasn't been merged yet despite being available for ~8 months.

In the meantime, you can disable "Force SSL" for each proxy host you need to renew.

tactmaster · 2024-04-15T07:19:30Z

Hello, Yes interesting, i think it block the process trying. So I had several proxies. One had force ssl on, one not. The one that didn't have it on. Also didn't work. All my proxies not have force off and now they all work. Ed Watson Tel: +46 702053827

…

On Sun, 14 Apr 2024 at 18:33, Blogshot ***@***.***> wrote: I believe that's more of an upstream issue, cf NginxProxyManager/nginx-proxy-manager#2881 <NginxProxyManager/nginx-proxy-manager#2881> Yes, it is. The reason is that the "Force SSL" option will redirect the HTTP challenges to HTTPS, which the integrated certbot doesnt support apparently. A pull request is open at NginxProxyManager/nginx-proxy-manager#3121 <NginxProxyManager/nginx-proxy-manager#3121>, but the issue hasn't been merged yet despite being available for ~8 months. In the meantime, you can disable "Force SSL" for each proxy host you need to renew. — Reply to this email directly, view it on GitHub <#400 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGBUHMXEL37OV3RPXY66F3Y5KVUHAVCNFSM6AAAAAAUU4EQB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJUGEYTKMJRGM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

github-actions · 2024-05-15T08:17:06Z

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

sulazix · 2024-05-16T15:23:25Z

Unstale :-)
Still needed to disable "force SSL" to work with DNS challenge.

dubhunter · 2024-05-16T16:28:58Z

Still a problem. But for me, only auto-update. Manual works fine even with Force SSL.

github-actions · 2024-06-17T08:18:11Z

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label May 10, 2023

github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label May 17, 2023

github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Jul 3, 2023

github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Jul 4, 2023

github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Aug 24, 2023

github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Aug 25, 2023

github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Sep 27, 2023

github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Sep 28, 2023

github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Jan 5, 2024

github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Jan 6, 2024

github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Feb 5, 2024

github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Feb 6, 2024

github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Apr 14, 2024

github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label Apr 15, 2024

github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label May 15, 2024

github-actions bot removed the stale There has not been activity on this issue or PR for quite some time. label May 17, 2024

github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label Jun 17, 2024

github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 25, 2024

number65259 mentioned this issue Jul 12, 2024

Addon installation corruption from SSL cert removal #586

Closed

github-actions bot locked and limited conversation to collaborators Jul 25, 2024

Uh oh!

SSL cert not updating #400

SSL cert not updating #400

Comments

tactmaster commented Feb 8, 2023

Problem/Motivation

Expected behavior

Actual behavior

Steps to reproduce

Proposed changes

SoulOfNoob commented Feb 8, 2023

Uh oh!

tactmaster commented Feb 8, 2023

Uh oh!

tactmaster commented Feb 15, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

eric10k93 commented Mar 7, 2023

Uh oh!

awdark commented Mar 23, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

TerrorBite commented Apr 9, 2023

Uh oh!

github-actions bot commented May 10, 2023

Uh oh!

ghost commented May 16, 2023

Uh oh!

fgibaux commented Jun 2, 2023

Uh oh!

github-actions bot commented Jul 3, 2023

Uh oh!

SiriosDev commented Jul 3, 2023

Uh oh!

awdark commented Jul 4, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Scags104 commented Jul 24, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Aug 24, 2023

Uh oh!

Scags104 commented Aug 24, 2023

Uh oh!

geigervlad commented Aug 27, 2023

Uh oh!

SiriosDev commented Aug 27, 2023

Uh oh!

github-actions bot commented Sep 27, 2023

Uh oh!

Scags104 commented Sep 27, 2023

Uh oh!

sulazix commented Sep 29, 2023

Uh oh!

eric10k93 commented Oct 4, 2023

Uh oh!

Scags104 commented Oct 5, 2023

Uh oh!

github-actions bot commented Jan 5, 2024

Uh oh!

tactmaster commented Jan 5, 2024 via email

Uh oh!

mathwizmf2009 commented Jan 5, 2024

Uh oh!

kaffeepause07 commented Jan 5, 2024

Uh oh!

akrigator commented Jan 5, 2024

Uh oh!

mathwizmf2009 commented Jan 5, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

akrigator commented Jan 5, 2024

Uh oh!

github-actions bot commented Feb 5, 2024

Uh oh!

SiriosDev commented Feb 5, 2024

Uh oh!

mathwizmf2009 commented Feb 16, 2024

Uh oh!

github-actions bot commented Apr 14, 2024

tactmaster commented Feb 15, 2023 •

edited

Loading

awdark commented Mar 23, 2023 •

edited

Loading

awdark commented Jul 4, 2023 •

edited

Loading

Scags104 commented Jul 24, 2023 •

edited

Loading

mathwizmf2009 commented Jan 5, 2024 •

edited

Loading

Blogshot commented Apr 14, 2024 •

edited

Loading