[Support] Nginx Proxy Manager (NPM) Official


Recommended Posts

On 11/17/2022 at 8:14 PM, mgutt said:

less /var/log/letsencrypt/letsencrypt.log

 

cat /var/log/letsencrypt/letsencrypt.log

 

1. 

022-11-19 01:05:45,409:DEBUG:certbot._internal.main:certbot version: 1.31.0
2022-11-19 01:05:45,409:DEBUG:certbot._internal.main:certbot version: 1.31.0
2022-11-19 01:05:45,409:DEBUG:certbot._internal.main:Location of certbot entry point: /usr/bin/certbot
2022-11-19 01:05:45,409:DEBUG:certbot._internal.main:Arguments: ['--force-renewal', '--config', '/etc/letsencrypt.ini', '--cert-name', 'npm-22', '--preferred-challenges', 'dns,http', '--no-random-sleep-on-renew', '--disable-hook-validation']
2022-11-19 01:05:45,409:DEBUG:certbot._internal.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2022-11-19 01:05:45,417:DEBUG:certbot._internal.log:Root logging level set at 30
2022-11-19 01:05:45,419:DEBUG:certbot._internal.display.obj:Notifying user: Processing /etc/letsencrypt/renewal/npm-22.conf
2022-11-19 01:05:45,421:ERROR:certbot._internal.renewal:Renewal configuration file /etc/letsencrypt/renewal/npm-22.conf is broken.
2022-11-19 01:05:45,421:ERROR:certbot._internal.renewal:The error was: expected /etc/letsencrypt/live/npm-22/cert.pem to be a symlink
Skipping.
2022-11-19 01:05:45,421:DEBUG:certbot._internal.renewal:Traceback was:
Traceback (most recent call last):
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/renewal.py", line 77, in _reconstitute
    renewal_candidate = storage.RenewableCert(full_path, config)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/storage.py", line 504, in __init__
    self._check_symlinks()
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/storage.py", line 578, in _check_symlinks
    "expected {0} to be a symlink".format(link))
certbot.errors.CertStorageError: expected /etc/letsencrypt/live/npm-22/cert.pem to be a symlink

2022-11-19 01:05:45,421:DEBUG:certbot._internal.display.obj:Notifying user: 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2022-11-19 01:05:45,422:DEBUG:certbot._internal.display.obj:Notifying user: No renewals were attempted.
2022-11-19 01:05:45,422:DEBUG:certbot._internal.display.obj:Notifying user: 
Additionally, the following renewal configurations were invalid: 
2022-11-19 01:05:45,422:DEBUG:certbot._internal.display.obj:Notifying user:   /etc/letsencrypt/renewal/npm-22.conf (parsefail)
2022-11-19 01:05:45,422:DEBUG:certbot._internal.display.obj:Notifying user: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2022-11-19 01:05:45,422:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
  File "/usr/bin/certbot", line 8, in <module>
    sys.exit(main())
  File "/opt/certbot/lib/python3.7/site-packages/certbot/main.py", line 19, in main
    return internal_main.main(cli_args)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/main.py", line 1744, in main
    return config.func(config, plugins)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/main.py", line 1630, in renew
    renewal.handle_renewal_request(config)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/renewal.py", line 511, in handle_renewal_request
    f"{len(renew_failures)} renew failure(s), {len(parse_failures)} parse failure(s)")
certbot.errors.Error: 0 renew failure(s), 1 parse failure(s)
:

 

2.

# cat /var/log/letsencrypt/letsencrypt.log
2022-11-19 01:05:45,409:DEBUG:certbot._internal.main:certbot version: 1.31.0
2022-11-19 01:05:45,409:DEBUG:certbot._internal.main:Location of certbot entry point: /usr/bin/certbot
2022-11-19 01:05:45,409:DEBUG:certbot._internal.main:Arguments: ['--force-renewal', '--config', '/etc/letsencrypt.ini', '--cert-name', 'npm-22', '--preferred-challenges', 'dns,http', '--no-random-sleep-on-renew', '--disable-hook-validation']
2022-11-19 01:05:45,409:DEBUG:certbot._internal.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2022-11-19 01:05:45,417:DEBUG:certbot._internal.log:Root logging level set at 30
2022-11-19 01:05:45,419:DEBUG:certbot._internal.display.obj:Notifying user: Processing /etc/letsencrypt/renewal/npm-22.conf
2022-11-19 01:05:45,421:ERROR:certbot._internal.renewal:Renewal configuration file /etc/letsencrypt/renewal/npm-22.conf is broken.
2022-11-19 01:05:45,421:ERROR:certbot._internal.renewal:The error was: expected /etc/letsencrypt/live/npm-22/cert.pem to be a symlink
Skipping.
2022-11-19 01:05:45,421:DEBUG:certbot._internal.renewal:Traceback was:
Traceback (most recent call last):
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/renewal.py", line 77, in _reconstitute
    renewal_candidate = storage.RenewableCert(full_path, config)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/storage.py", line 504, in __init__
    self._check_symlinks()
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/storage.py", line 578, in _check_symlinks
    "expected {0} to be a symlink".format(link))
certbot.errors.CertStorageError: expected /etc/letsencrypt/live/npm-22/cert.pem to be a symlink

2022-11-19 01:05:45,421:DEBUG:certbot._internal.display.obj:Notifying user: 
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2022-11-19 01:05:45,422:DEBUG:certbot._internal.display.obj:Notifying user: No renewals were attempted.
2022-11-19 01:05:45,422:DEBUG:certbot._internal.display.obj:Notifying user: 
Additionally, the following renewal configurations were invalid: 
2022-11-19 01:05:45,422:DEBUG:certbot._internal.display.obj:Notifying user:   /etc/letsencrypt/renewal/npm-22.conf (parsefail)
2022-11-19 01:05:45,422:DEBUG:certbot._internal.display.obj:Notifying user: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
2022-11-19 01:05:45,422:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
  File "/usr/bin/certbot", line 8, in <module>
    sys.exit(main())
  File "/opt/certbot/lib/python3.7/site-packages/certbot/main.py", line 19, in main
    return internal_main.main(cli_args)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/main.py", line 1744, in main
    return config.func(config, plugins)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/main.py", line 1630, in renew
    renewal.handle_renewal_request(config)
  File "/opt/certbot/lib/python3.7/site-packages/certbot/_internal/renewal.py", line 511, in handle_renewal_request
    f"{len(renew_failures)} renew failure(s), {len(parse_failures)} parse failure(s)")
certbot.errors.Error: 0 renew failure(s), 1 parse failure(s)
2022-11-19 01:05:45,422:ERROR:certbot._internal.log:0 renew failure(s), 1 parse failure(s)

Link to comment
28 minutes ago, Evilernie said:

2022-11-19 01:05:45,419:DEBUG:certbot._internal.display.obj:Notifying user: Processing /etc/letsencrypt/renewal/npm-22.conf
2022-11-19 01:05:45,421:ERROR:certbot._internal.renewal:Renewal configuration file /etc/letsencrypt/renewal/npm-22.conf is broken.
2022-11-19 01:05:45,421:ERROR:certbot._internal.renewal:The error was: expected /etc/letsencrypt/live/npm-22/cert.pem to be a symlink
Skipping.

 

Did you restore your appdata through a backup or similar? As you can see it wants a symlink. Or is this file even missing?

 

Link to comment

at the moment, yesterday i wanted to transfer the cache drive, but there was a failure. So I needed to backup it. I made a new docker without the Backup to eliminate the problem, start and make it new, but with this I could not reach a host, I use the same settings but I could not reach the sites. 

So I used the Backup and I can reach my sides, but no new ssl.

 

What do you mean with file even missing. Was the hole backup

Edited by Evilernie
Link to comment
53 minutes ago, mgutt said:

The backup is broken somehow. How do you create it? Either it kills symlinks or it does not respect user permissions.

I used 

 

Backup/Restore Appdata

 

The Problem with SSL update was befor the backup. 

 

Okay, wenn there is a problem, with a new setup it was not running, what can I do?

 

The owner was my account, I changed it to "nobody", permissions are "drwxrwxrwx"

Link to comment
1 hour ago, Evilernie said:

The owner was my account, I changed it to "nobody", permissions are "drwxrwxrwx"

You are not allowed to change user permissions inside of appdata. This kills every container.

 

1 hour ago, Evilernie said:

Okay, wenn there is a problem, with a new setup it was not running, what can I do?

Did you really delete the old appdata npm folder? Use clean up appdata Plugin. Then start from the beginning. Any new SSL issue needs to be checked then.

Link to comment
5 hours ago, mgutt said:

You are not allowed to change user permissions inside of appdata. This kills every container.

 

Did you really delete the old appdata npm folder? Use clean up appdata Plugin. Then start from the beginning. Any new SSL issue needs to be checked then.

okay, can I rename the appdata, after stopping docker, use a Backup from 

 

Backup/Restore Appdata

 

and then delete the npm folder and then restart the docker? Or must I delete the docker image too?

Link to comment
2 hours ago, Evilernie said:

Backup/Restore Appdata

The downside of this plugin is, that it does not allow to restore single containers.

 

That's why I would extract the files manually like this:

 

mkdir /mnt/user/appdata_restore

tar -xvf /mnt/path/to/bakup.tar -C /mnt/user/appdata_restore

 

Now stop NPM.

 

Rename the current dir:

mv /mnt/user/appdata/Nginx-Proxy-Manager-Official /mnt/user/appdata/Nginx-Proxy-Manager-Official_old

 

Move the backup:

mv /mnt/user/appdata_restore/Nginx-Proxy-Manager-Official /mnt/user/appdata/Nginx-Proxy-Manager-Official

 

Start NPM container

 

But: This probably won't work if your backup is older than your used container version. How old is your backup and did you update the container in the meantime? "Latest" = version 2.9.19 is only 12 days old:

https://hub.docker.com/r/jc21/nginx-proxy-manager/tags

 

To delete the container including image and install the container with a specific version by editing the container and replace :latest against for example :2.9.18 (which was released 8 month ago).

 

After that check if everything works. If yes, create a backup. Then replace against :latest and try the update.

Link to comment

Installing your docker but WebUI is not working:
 

Generating a RSA private key
..................................................+++++
.+++++
writing new private key to '/data/nginx/dummykey.pem'
-----
[services.d] starting services
[services.d] done.
Generating dummy SSL certificate...
Complete
❯ Enabling IPV6 in hosts: /etc/nginx/conf.d
  ❯ /etc/nginx/conf.d/default.conf
  ❯ /etc/nginx/conf.d/include/assets.conf
  ❯ /etc/nginx/conf.d/include/block-exploits.conf
  ❯ /etc/nginx/conf.d/include/force-ssl.conf
  ❯ /etc/nginx/conf.d/include/ip_ranges.conf
  ❯ /etc/nginx/conf.d/include/letsencrypt-acme-challenge.conf
  ❯ /etc/nginx/conf.d/include/proxy.conf
  ❯ /etc/nginx/conf.d/include/ssl-ciphers.conf
  ❯ /etc/nginx/conf.d/include/resolvers.conf
  ❯ /etc/nginx/conf.d/production.conf
❯ Enabling IPV6 in hosts: /data/nginx
[11/29/2022] [2:06:51 PM] [Global   ] › ℹ  info      Generating SQLite knex configuration
[11/29/2022] [2:06:51 PM] [Global   ] › ⬤  debug     Wrote db configuration to config file: ./config/production.json
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      Current database version: none
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] auth Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] user Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] user_permission Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] proxy_host Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] redirection_host Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] dead_host Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] stream Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] access_list Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] certificate Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] access_list_auth Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [initial-schema] audit_log Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [websockets] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [websockets] proxy_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [forward_host] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [forward_host] proxy_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [http2_support] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [http2_support] proxy_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [http2_support] redirection_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [http2_support] dead_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [forward_scheme] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [forward_scheme] proxy_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [disabled] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [disabled] proxy_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [disabled] redirection_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [disabled] dead_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [disabled] stream Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [custom_locations] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [custom_locations] proxy_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [hsts] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [hsts] proxy_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [hsts] redirection_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [hsts] dead_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [settings] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [settings] setting Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [access_list_client] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [access_list_client] access_list_client Table created
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [access_list_client] access_list Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [access_list_client_fix] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [access_list_client_fix] access_list Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [pass_auth] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [pass_auth] access_list Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [redirection_scheme] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [redirection_scheme] redirection_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [redirection_status_code] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [redirection_status_code] redirection_host Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [stream_domain] stream Table altered
[11/29/2022] [2:06:53 PM] [Migrate  ] › ℹ  info      [stream_domain] Migrating Up...
[11/29/2022] [2:06:53 PM] [Setup    ] › ℹ  info      Creating a new JWT key pair...
[11/29/2022] [2:06:58 PM] [Setup    ] › ℹ  info      Wrote JWT key pair to config file: /app/config/production.json
[11/29/2022] [2:06:58 PM] [Setup    ] › ℹ  info      Creating a new user: [email protected] with password: changeme
[11/29/2022] [2:06:58 PM] [Setup    ] › ℹ  info      Initial admin setup completed
[11/29/2022] [2:06:58 PM] [Setup    ] › ℹ  info      Default settings added
[11/29/2022] [2:06:58 PM] [Setup    ] › ℹ  info      Logrotate Timer initialized
[11/29/2022] [2:06:59 PM] [Setup    ] › ℹ  info      Logrotate completed.
[11/29/2022] [2:06:59 PM] [IP Ranges] › ℹ  info      Fetching IP Ranges from online services...
[11/29/2022] [2:06:59 PM] [IP Ranges] › ℹ  info      Fetching https://ip-ranges.amazonaws.com/ip-ranges.json
[11/29/2022] [2:06:59 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v4
[11/29/2022] [2:06:59 PM] [IP Ranges] › ℹ  info      Fetching https://www.cloudflare.com/ips-v6
[11/29/2022] [2:06:59 PM] [SSL      ] › ℹ  info      Let's Encrypt Renewal Timer initialized
[11/29/2022] [2:06:59 PM] [SSL      ] › ℹ  info      Renewing SSL certs close to expiry...
[11/29/2022] [2:06:59 PM] [IP Ranges] › ℹ  info      IP Ranges Renewal Timer initialized
[11/29/2022] [2:06:59 PM] [Global   ] › ℹ  info      Backend PID 245 listening on port 3000 ...
[11/29/2022] [2:07:01 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[11/29/2022] [2:07:01 PM] [SSL      ] › ℹ  info      Renew Complete


Something that I miss?

Link to comment

I'm having an issue where I hadn't used some of my subdomains for some time with nextcloud. I have been using a duckdns link for when my public IP changed. Now I am getting warnings about some certificates expiring and I've found that none of subdomains I've had for years now with Google are working however my duckdns link is still accessing nextcloud properly and when I use a browser to try the subdomains I'm getting that "congratulations you've successfully started the Nginx Proxy Manager". So if from a browser off my LAN my duckdns link is working what is causing my subdomains to not load. For example b***.***server.com and *****.duckdns.org both go to nextcloud but only duckdns loads it. 

Thanks in advance for any help!!

Edited by DuneJeeper
Misspelled and bad grammar
Link to comment

Here is an error log from the letsencrypt file inside of the NGINX appdata folder after deleting the google subdomain and the host in NPM and then redoing both

 

2022-12-04 06:38:37,151:DEBUG:certbot._internal.main:certbot version: 1.27.0
2022-12-04 06:38:37,151:DEBUG:certbot._internal.main:Location of certbot entry point: /usr/bin/certbot
2022-12-04 06:38:37,151:DEBUG:certbot._internal.main:Arguments: ['--config', '/etc/letsencrypt.ini', '--cert-name', 'npm-15', '--agree-tos', '--authenticator', 'webroot', '--email', '[email protected]', '--preferred-challenges', 'dns,http', '--domains', 'vaultwarden.jsXXXXX.com']
2022-12-04 06:38:37,151:DEBUG:certbot._internal.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#manual,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
2022-12-04 06:38:37,942:DEBUG:certbot._internal.log:Root logging level set at 30
2022-12-04 06:38:37,947:DEBUG:certbot._internal.plugins.selection:Requested authenticator webroot and installer None
2022-12-04 06:38:37,960:DEBUG:certbot._internal.plugins.selection:Single candidate plugin: * webroot
Description: Place files in webroot directory
Interfaces: Authenticator, Plugin
Entry point: webroot = certbot._internal.plugins.webroot:Authenticator
Initialized: <certbot._internal.plugins.webroot.Authenticator object at 0x146847b8dbe0>
Prep: True
2022-12-04 06:38:37,961:DEBUG:certbot._internal.plugins.selection:Selected authenticator <certbot._internal.plugins.webroot.Authenticator object at 0x146847b8dbe0> and installer None
2022-12-04 06:38:37,962:INFO:certbot._internal.plugins.selection:Plugins selected: Authenticator webroot, Installer None
2022-12-04 06:38:38,212:DEBUG:certbot._internal.main:Picked account: <Account(RegistrationResource(body=Registration(key=None, contact=(), agreement=None, status=None, terms_of_service_agreed=None, only_return_existing=None, external_account_binding=None), uri='https://acme-v02.api.letsencrypt.org/acme/acct/244684430', new_authzr_uri=None, terms_of_service=None), ff47a0a8b3b4440b514c9676077dc033, Meta(creation_dt=datetime.datetime(2021, 10, 18, 21, 30, 9, tzinfo=<UTC>), creation_host='610dfc3962ef', register_to_eff=None))>
2022-12-04 06:38:38,214:DEBUG:acme.client:Sending GET request to https://acme-v02.api.letsencrypt.org/directory.
2022-12-04 06:38:38,219:DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org:443
2022-12-04 06:38:38,381:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "GET /directory HTTP/1.1" 200 659
2022-12-04 06:38:38,383:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Sun, 04 Dec 2022 12:38:38 GMT
Content-Type: application/json
Content-Length: 659
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800

{
  "WevIWKAr5WU": "https://community.letsencrypt.org/t/adding-random-entries-to-the-directory/33417",
  "keyChange": "https://acme-v02.api.letsencrypt.org/acme/key-change",
  "meta": {
    "caaIdentities": [
      "letsencrypt.org"
    ],
    "termsOfService": "https://letsencrypt.org/documents/LE-SA-v1.3-September-21-2022.pdf",
    "website": "https://letsencrypt.org"
  },
  "newAccount": "https://acme-v02.api.letsencrypt.org/acme/new-acct",
  "newNonce": "https://acme-v02.api.letsencrypt.org/acme/new-nonce",
  "newOrder": "https://acme-v02.api.letsencrypt.org/acme/new-order",
  "revokeCert": "https://acme-v02.api.letsencrypt.org/acme/revoke-cert"
}
2022-12-04 06:38:38,385:DEBUG:certbot._internal.display.obj:Notifying user: Requesting a certificate for vaultwarden.XXXXX.com
2022-12-04 06:38:38,397:DEBUG:certbot.crypto_util:Generating ECDSA key (2048 bits): /etc/letsencrypt/keys/0004_key-certbot.pem
2022-12-04 06:38:38,410:DEBUG:certbot.crypto_util:Creating CSR: /etc/letsencrypt/csr/0004_csr-certbot.pem
2022-12-04 06:38:38,415:DEBUG:acme.client:Requesting fresh nonce
2022-12-04 06:38:38,415:DEBUG:acme.client:Sending HEAD request to https://acme-v02.api.letsencrypt.org/acme/new-nonce.
2022-12-04 06:38:38,468:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "HEAD /acme/new-nonce HTTP/1.1" 200 0
2022-12-04 06:38:38,470:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Sun, 04 Dec 2022 12:38:38 GMT
Connection: keep-alive
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Replay-Nonce: 5CA2zA_muTGdjlNqLW3tXuuce14PoKWDX_7cT8XZ6FKy514
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800


2022-12-04 06:38:38,470:DEBUG:acme.client:Storing nonce: 5CA2zA_muTGdjlNqLW3tXuuce14PoKWDX_7cT8XZ6FKy514
2022-12-04 06:38:38,471:DEBUG:acme.client:JWS payload:
b'{\n  "identifiers": [\n    {\n      "type": "dns",\n      "value": "vaultwarden.XXXXX.com"\n    }\n  ]\n}'
2022-12-04 06:38:38,480:DEBUG:acme.client:Sending POST request to https://acme-v02.api.letsencrypt.org/acme/new-order:
{
  "protected": "eyJhbGciOiAiUlMyNTYiLCAia2lkIjogImh0dHBzOi8vYWNtZS12MDIuYXBpLmxldHNlbmNyeXB0Lm9yZy9hY21lL2FjY3QvMjQ0Njg0NDMwIiwgIm5vbmNlIjogIjVDQTJ6QV9tdVRHZGpsTnFMVzN0WHV1Y2UxNFBvS1dEWF83Y1Q4WFo2Rkt5NTE0IiwgInVybCI6ICJodHRwczovL2FjbWUtdjAyLmFwaS5sZXRzZW5jcnlwdC5vcmcvYWNtZS9uZXctb3JkZXIifQ",
  "signature": "AGiv5F7QRfo6PF87gLcBOjzJV0vHekURy8FxVwC9II3t6DXahB_h8N8zZzucHqqI8s28MFqaCKG0UhXl5MsYScYdf2Ecei0KQYUvBUYntL7HE840nYRKlLtYOQ2Q6D6ZzFuwWLcOmBJ47oziDfZZ_GiXrbgFoTw9GWD-jndBKh5cM1Svd2SYFIH3cQkg-YElcLmDbdHxRLzxt7M2_3nH5Eco9XtAT2-gr-pJVt7T5JnFPYDuc9vp3zesj8Oq2ylLJHHUrhnzedVZiyEf5HKWf5W8L9MduAHjKTX3SGCSAtUPPHaJ-qqLpXwY3R8jSDoP_-iZEr9A0eGqew32FLBA7Q",
  "payload": "ewogICJpZGVudGlmaWVycyI6IFsKICAgIHsKICAgICAgInR5cGUiOiAiZG5zIiwKICAgICAgInZhbHVlIjogInZhdWx0d2FyZGVuLmpzYnNlcnZlci5jb20iCiAgICB9CiAgXQp9"
}
2022-12-04 06:38:38,679:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "POST /acme/new-order HTTP/1.1" 201 350
2022-12-04 06:38:38,681:DEBUG:acme.client:Received response:
HTTP 201
Server: nginx
Date: Sun, 04 Dec 2022 12:38:38 GMT
Content-Type: application/json
Content-Length: 350
Connection: keep-alive
Boulder-Requester: 244684430
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Location: https://acme-v02.api.letsencrypt.org/acme/order/244684430/150257178297
Replay-Nonce: 371Cq1DKlCrmoBqtyvsiKOklNyU3_ZfKvRRlQmn0CK72WQ8
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800

{
  "status": "pending",
  "expires": "2022-12-11T12:38:38Z",
  "identifiers": [
    {
      "type": "dns",
      "value": "vaultwarden.XXXXX.com"
    }
  ],
  "authorizations": [
    "https://acme-v02.api.letsencrypt.org/acme/authz-v3/183831876757"
  ],
  "finalize": "https://acme-v02.api.letsencrypt.org/acme/finalize/244684430/150257178297"
}
2022-12-04 06:38:38,681:DEBUG:acme.client:Storing nonce: 371Cq1DKlCrmoBqtyvsiKOklNyU3_ZfKvRRlQmn0CK72WQ8
2022-12-04 06:38:38,682:DEBUG:acme.client:JWS payload:
b''
2022-12-04 06:38:38,688:DEBUG:acme.client:Sending POST request to https://acme-v02.api.letsencrypt.org/acme/authz-v3/183831876757:
{
  "protected": "eyJhbGciOiAiUlMyNTYiLCAia2lkIjogImh0dHBzOi8vYWNtZS12MDIuYXBpLmxldHNlbmNyeXB0Lm9yZy9hY21lL2FjY3QvMjQ0Njg0NDMwIiwgIm5vbmNlIjogIjM3MUNxMURLbENybW9CcXR5dnNpS09rbE55VTNfWmZLdlJSbFFtbjBDSzcyV1E4IiwgInVybCI6ICJodHRwczovL2FjbWUtdjAyLmFwaS5sZXRzZW5jcnlwdC5vcmcvYWNtZS9hdXRoei12My8xODM4MzE4NzY3NTcifQ",
  "signature": "MJg0fdiotGsLGY0OtDLLHrsgaDinsOYK37uXLhV9uoComDYu1z3VY4l84Uu75m5-CR-RB1hGrDSoX2K1yqqfHino783SMINzRfTfoxyFhLkrvG4j3vX6FZB7NfpiGv7bxbLnWDHO9XHcJ7pdwHz4Uf_HMa-KsBwlwGn8oqNoEamO1dwqfedmEFO4yNj4f-yvGyL7PjwBLeujeuG0bx6JQqfdSbq3pfnEOgkQGlvPd-PZ2nL1HHdg4DdjZIx_gxIIke0zs8gMTnjP2tizO6nBbpHMLMvipGEgCYxnPy1hTOVpK-GYHpoUzoc4bT7PEvyqhrvIsBAgCSTmYL6S-96X7Q",
  "payload": ""
}
2022-12-04 06:38:38,764:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "POST /acme/authz-v3/183831876757 HTTP/1.1" 200 809
2022-12-04 06:38:38,765:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Sun, 04 Dec 2022 12:38:38 GMT
Content-Type: application/json
Content-Length: 809
Connection: keep-alive
Boulder-Requester: 244684430
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Replay-Nonce: 1DFA1Zkxib13g0N_a87Ib88r_FTzhGEJKWuXsp6aN6otrlY
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800

{
  "identifier": {
    "type": "dns",
    "value": "vaultwarden.XXXXX.com"
  },
  "status": "pending",
  "expires": "2022-12-11T12:38:38Z",
  "challenges": [
    {
      "type": "http-01",
      "status": "pending",
      "url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/183831876757/f0OwpA",
      "token": "5lz_b5iRNiFt7mWfO88xUuR7J4E7zurpem2-d2IZGH4"
    },
    {
      "type": "dns-01",
      "status": "pending",
      "url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/183831876757/auEevQ",
      "token": "5lz_b5iRNiFt7mWfO88xUuR7J4E7zurpem2-d2IZGH4"
    },
    {
      "type": "tls-alpn-01",
      "status": "pending",
      "url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/183831876757/5OAA5Q",
      "token": "5lz_b5iRNiFt7mWfO88xUuR7J4E7zurpem2-d2IZGH4"
    }
  ]
}
2022-12-04 06:38:38,766:DEBUG:acme.client:Storing nonce: 1DFA1Zkxib13g0N_a87Ib88r_FTzhGEJKWuXsp6aN6otrlY
2022-12-04 06:38:38,767:INFO:certbot._internal.auth_handler:Performing the following challenges:
2022-12-04 06:38:38,768:INFO:certbot._internal.auth_handler:http-01 challenge for vaultwarden.jsbserver.com
2022-12-04 06:38:38,769:INFO:certbot._internal.plugins.webroot:Using the webroot path /data/letsencrypt-acme-challenge for all unmatched domains.
2022-12-04 06:38:38,769:DEBUG:certbot._internal.plugins.webroot:Creating root challenges validation dir at /data/letsencrypt-acme-challenge/.well-known/acme-challenge
2022-12-04 06:38:38,774:DEBUG:certbot._internal.plugins.webroot:Attempting to save validation to /data/letsencrypt-acme-challenge/.well-known/acme-challenge/5lz_b5iRNiFt7mWfO88xUuR7J4E7zurpem2-d2IZGH4
2022-12-04 06:38:38,776:DEBUG:acme.client:JWS payload:
b'{}'
2022-12-04 06:38:38,781:DEBUG:acme.client:Sending POST request to https://acme-v02.api.letsencrypt.org/acme/chall-v3/183831876757/f0OwpA:
{
  "protected": "eyJhbGciOiAiUlMyNTYiLCAia2lkIjogImh0dHBzOi8vYWNtZS12MDIuYXBpLmxldHNlbmNyeXB0Lm9yZy9hY21lL2FjY3QvMjQ0Njg0NDMwIiwgIm5vbmNlIjogIjFERkExWmt4aWIxM2cwTl9hODdJYjg4cl9GVHpoR0VKS1d1WHNwNmFONm90cmxZIiwgInVybCI6ICJodHRwczovL2FjbWUtdjAyLmFwaS5sZXRzZW5jcnlwdC5vcmcvYWNtZS9jaGFsbC12My8xODM4MzE4NzY3NTcvZjBPd3BBIn0",
  "signature": "lIt_Tsfsj4ANGfGjTl9iCK41f0grLPz_3oC1EKbXY1oC3wgBcWmW0I2WhCHgQjxNK8obQMK6o2-RDc-1bDp41j1f_PiGVnVqf4oCEOIgv83NjDlMuXMUvhAKxi5Ek-M-rpQb5nI92Sd9j5_DMJ5SunzCsns_ln-5RRm5bPfRla6ailt023OcDA-_k7JqhdmLwZKN9mzFDlZZG99wDpoN9q8R9PyCWOtYYRl3ucM0h_8KzM8VTKt5wtVtmtdiuc7lYJAxmgAwtiT4Z4_0Evu5lfRddtrM098--VbfvbDFfafNC5VSbGdVG94KE_EXYfJnBycDJ96t26LenNMgJvDhzQ",
  "payload": "e30"
}
2022-12-04 06:38:38,838:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "POST /acme/chall-v3/183831876757/f0OwpA HTTP/1.1" 200 187
2022-12-04 06:38:38,839:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Sun, 04 Dec 2022 12:38:38 GMT
Content-Type: application/json
Content-Length: 187
Connection: keep-alive
Boulder-Requester: 244684430
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index", <https://acme-v02.api.letsencrypt.org/acme/authz-v3/183831876757>;rel="up"
Location: https://acme-v02.api.letsencrypt.org/acme/chall-v3/183831876757/f0OwpA
Replay-Nonce: 1DFAY52gw7ubiatPtDC8A01gOji0v4OZdZWxVoLreItsCjA
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800

{
  "type": "http-01",
  "status": "pending",
  "url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/183831876757/f0OwpA",
  "token": "5lz_b5iRNiFt7mWfO88xUuR7J4E7zurpem2-d2IZGH4"
}
2022-12-04 06:38:38,840:DEBUG:acme.client:Storing nonce: 1DFAY52gw7ubiatPtDC8A01gOji0v4OZdZWxVoLreItsCjA
2022-12-04 06:38:38,841:INFO:certbot._internal.auth_handler:Waiting for verification...
2022-12-04 06:38:39,842:DEBUG:acme.client:JWS payload:
b''
2022-12-04 06:38:39,848:DEBUG:acme.client:Sending POST request to https://acme-v02.api.letsencrypt.org/acme/authz-v3/183831876757:
{
  "protected": "eyJhbGciOiAiUlMyNTYiLCAia2lkIjogImh0dHBzOi8vYWNtZS12MDIuYXBpLmxldHNlbmNyeXB0Lm9yZy9hY21lL2FjY3QvMjQ0Njg0NDMwIiwgIm5vbmNlIjogIjFERkFZNTJndzd1YmlhdFB0REM4QTAxZ09qaTB2NE9aZFpXeFZvTHJlSXRzQ2pBIiwgInVybCI6ICJodHRwczovL2FjbWUtdjAyLmFwaS5sZXRzZW5jcnlwdC5vcmcvYWNtZS9hdXRoei12My8xODM4MzE4NzY3NTcifQ",
  "signature": "Hm3jP0ZqcRvG2EE4dXqX54OOyvN6igKFK8pIyObuElcdijyfYbS0Tc81ekXc34JepaVZyyMukt47QYdOoFv3p4kACFdYFDuJVIJ4mh16XNVYFPub7zo9du7PHoB2hJ_y_CMhdqKbdYX5NrYyAsxxVn4_e0srN1aCOFNj59F0yOLPWJYF9w3F7sAUAPWU21agnUVdHNAMhAOe50xwxUd_W3V7HJDJDXuvQlqFqEd7nqJCXDp0GsuLndXONc3Imbv4j8_E7vAqaz0ExhScWtPSA9dpHu9Px5z7Nu0aw80coReZs9nAYvyQDTQUajlHfRzgd3XT2rL5uxXCAUid-I59_Q",
  "payload": ""
}
2022-12-04 06:38:39,922:DEBUG:urllib3.connectionpool:https://acme-v02.api.letsencrypt.org:443 "POST /acme/authz-v3/183831876757 HTTP/1.1" 200 1130
2022-12-04 06:38:39,924:DEBUG:acme.client:Received response:
HTTP 200
Server: nginx
Date: Sun, 04 Dec 2022 12:38:39 GMT
Content-Type: application/json
Content-Length: 1130
Connection: keep-alive
Boulder-Requester: 244684430
Cache-Control: public, max-age=0, no-cache
Link: <https://acme-v02.api.letsencrypt.org/directory>;rel="index"
Replay-Nonce: 371CIPOmXjwa3h2D0ehLiA3F4Wdycs-bA9Nnz93C87hWxrI
X-Frame-Options: DENY
Strict-Transport-Security: max-age=604800

{
  "identifier": {
    "type": "dns",
    "value": "vaultwarden.XXXXX.com"
  },
  "status": "invalid",
  "expires": "2022-12-11T12:38:38Z",
  "challenges": [
    {
      "type": "http-01",
      "status": "invalid",
      "error": {
        "type": "urn:ietf:params:acme:error:unauthorized",
        "detail": "2a00:1450:400e:80f::2013: Invalid response from http://vaultwarden.XXXXX.com/.well-known/acme-challenge/5lz_b5iRNiFt7mWfO88xUuR7J4E7zurpem2-d2IZGH4: 404",
        "status": 403
      },
      "url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/183831876757/f0OwpA",
      "token": "5lz_b5iRNiFt7mWfO88xUuR7J4E7zurpem2-d2IZGH4",
      "validationRecord": [
        {
          "url": "http://vaultwarden.XXXXX.com/.well-known/acme-challenge/5lz_b5iRNiFt7mWfO88xUuR7J4E7zurpem2-d2IZGH4",
          "hostname": "vaultwarden.XXXXX.com",
          "port": "80",
          "addressesResolved": [
            "142.250.72.51",
            "2a00:1450:400e:80f::2013"
          ],
          "addressUsed": "2a00:1450:400e:80f::2013"
        }
      ],
      "validated": "2022-12-04T12:38:38Z"
    }
  ]
}
2022-12-04 06:38:39,924:DEBUG:acme.client:Storing nonce: 371CIPOmXjwa3h2D0ehLiA3F4Wdycs-bA9Nnz93C87hWxrI
2022-12-04 06:38:39,925:INFO:certbot._internal.auth_handler:Challenge failed for domain vaultwarden.XXXXX.com
2022-12-04 06:38:39,926:INFO:certbot._internal.auth_handler:http-01 challenge for vaultwarden.XXXXX.com
2022-12-04 06:38:39,927:DEBUG:certbot._internal.display.obj:Notifying user: 
Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: vaultwarden.XXXXX.com
  Type:   unauthorized
  Detail: 2a00:1450:400e:80f::2013: Invalid response from http://vaultwarden.XXXXX.com/.well-known/acme-challenge/5lz_b5iRNiFt7mWfO88xUuR7J4E7zurpem2-d2IZGH4: 404

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.

2022-12-04 06:38:39,928:DEBUG:certbot._internal.error_handler:Encountered exception:
Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/certbot/_internal/auth_handler.py", line 106, in handle_authorizations
    self._poll_authorizations(authzrs, max_retries, best_effort)
  File "/usr/lib/python3.9/site-packages/certbot/_internal/auth_handler.py", line 206, in _poll_authorizations
    raise errors.AuthorizationError('Some challenges have failed.')
certbot.errors.AuthorizationError: Some challenges have failed.

2022-12-04 06:38:39,928:DEBUG:certbot._internal.error_handler:Calling registered functions
2022-12-04 06:38:39,929:INFO:certbot._internal.auth_handler:Cleaning up challenges
2022-12-04 06:38:39,929:DEBUG:certbot._internal.plugins.webroot:Removing /data/letsencrypt-acme-challenge/.well-known/acme-challenge/5lz_b5iRNiFt7mWfO88xUuR7J4E7zurpem2-d2IZGH4
2022-12-04 06:38:39,931:DEBUG:certbot._internal.plugins.webroot:All challenges cleaned up
2022-12-04 06:38:39,932:DEBUG:certbot._internal.log:Exiting abnormally:
Traceback (most recent call last):
  File "/usr/bin/certbot", line 8, in <module>
    sys.exit(main())
  File "/usr/lib/python3.9/site-packages/certbot/main.py", line 19, in main
    return internal_main.main(cli_args)
  File "/usr/lib/python3.9/site-packages/certbot/_internal/main.py", line 1744, in main
    return config.func(config, plugins)
  File "/usr/lib/python3.9/site-packages/certbot/_internal/main.py", line 1591, in certonly
    lineage = _get_and_save_cert(le_client, config, domains, certname, lineage)
  File "/usr/lib/python3.9/site-packages/certbot/_internal/main.py", line 141, in _get_and_save_cert
    lineage = le_client.obtain_and_enroll_certificate(domains, certname)
  File "/usr/lib/python3.9/site-packages/certbot/_internal/client.py", line 513, in obtain_and_enroll_certificate
    cert, chain, key, _ = self.obtain_certificate(domains)
  File "/usr/lib/python3.9/site-packages/certbot/_internal/client.py", line 441, in obtain_certificate
    orderr = self._get_order_and_authorizations(csr.data, self.config.allow_subset_of_names)
  File "/usr/lib/python3.9/site-packages/certbot/_internal/client.py", line 493, in _get_order_and_authorizations
    authzr = self.auth_handler.handle_authorizations(orderr, self.config, best_effort)
  File "/usr/lib/python3.9/site-packages/certbot/_internal/auth_handler.py", line 106, in handle_authorizations
    self._poll_authorizations(authzrs, max_retries, best_effort)
  File "/usr/lib/python3.9/site-packages/certbot/_internal/auth_handler.py", line 206, in _poll_authorizations
    raise errors.AuthorizationError('Some challenges have failed.')
certbot.errors.AuthorizationError: Some challenges have failed.
2022-12-04 06:38:39,935:ERROR:certbot._internal.log:Some challenges have failed.

 

Link to comment
3 hours ago, DuneJeeper said:
  "challenges": [
    {
      "type": "http-01",
      "status": "invalid",
      "error": {
        "type": "urn:ietf:params:acme:error:unauthorized",
        "detail": "2a00:1450:xxxx:xxx::xxx: Invalid response from http://vaultwarden.XXXXX.com/.well-known/acme-challenge/xxx-d2IZGH4: 404",
        "status": 403
      },
      "url": "https://acme-v02.api.letsencrypt.org/acme/chall-v3/183831876757/f0OwpA",
      "token": "xxx-d2IZGH4",
      "validationRecord": [
        {
          "url": "http://vaultwarden.XXXXX.com/.well-known/acme-challenge/xxx-d2IZGH4",
          "hostname": "vaultwarden.XXXXX.com",
          "port": "80",
          "addressesResolved": [
            "142.250.xxx.xxx",
            "2a00:1450:xxx:xxx::xxx"
          ],
          "addressUsed": "2a00:1450:xxx:xxx::xxx"
        }
      ],
      "validated": "2022-12-04T12:38:38Z"
    }

 

 

As you can see it used the IPv6 address 2a00... and it seems that this IPv6 address does not target your NPM container. Try to open http://[2a00:1450.....]/ through your browser. It must return the NPM welcome page.

Link to comment
3 hours ago, mgutt said:

 

As you can see it used the IPv6 address 2a00... and it seems that this IPv6 address does not target your NPM container. Try to open http://[2a00:1450.....]/ through your browser. It must return the NPM welcome page.

I'm sorry I purchased unRAID to host a cloud for my family and I'm not totally familiar with what you're saying. I'm not in IT. I appreciate you replying but if you could point me towards correcting this I'd appreciate it! Thanks!! I don't want to rely on duckdns alone.

Link to comment
4 hours ago, mgutt said:

 

As you can see it used the IPv6 address 2a00... and it seems that this IPv6 address does not target your NPM container. Try to open http://[2a00:1450.....]/ through your browser. It must return the NPM welcome page.

When I type that 2a00:1450:400e:80f::2013 in my browser it just launces a google search and tells me it's an address in the Netherlands 

Link to comment
1 hour ago, DuneJeeper said:

When I type that 2a00:1450:400e:80f::2013 in my browser

You must write http://[] and then put the IPv6 between the brackets (they are important).

 

2 hours ago, DuneJeeper said:

I'm sorry I purchased unRAID to host a cloud for my family and I'm not totally familiar with what you're saying

Then I suggest to disable IPv6 in your router and use only IPv4. This is much easier.

 

After that try to open http://1.2.3.4 while replacing 1.2.3.4 against your public IPv4 (yes, this time without brackets). If you don't see loading NPM, then you probably don't have a public IPv4. Then ask your provider if this is changeable. If not: Give up. No joke. Providing a server behind a proxified IPv4 is only possible by renting an VPS server, setting up a tunnel through IPv6 and so on... This is the most complicated setup.

 

 

If you have a public IPv4 and you still want IPv6, then:

- NPM must use the host network

- NPM must use port 443 and port 80 (which means you forward port 80 to 80 and 443 to 443 in your router)

- the Unraid GUI must be changed to different ports like 5000 and 5001

- your DDNS domain needs an AAAA DNS record with the IPv6 of your NPM container

- if you are using a DDNS container to update the DNS records, it must support IPv6 and run in host network, too

 

Link to comment
4 hours ago, mgutt said:

You must write http://[] and then put the IPv6 between the brackets (they are important).

 

After that try to open http://1.2.3.4 while replacing 1.2.3.4 against your public IPv4 (yes, this time without brackets). If you don't see loading NPM, then you probably don't have a public IPv4. Then ask your provider if this is changeable. If not: Give up. No joke. Providing a server behind a proxified IPv4 is only possible by renting an VPS server, setting up a tunnel through IPv6 and so on... This is the most complicated setup.

 

 

 

 

The address in brackets didn't load a page. "This site can't be reached" "ERR_ADDRESS_UNREACHABLE"

IPv6 is toggled off on my router. It's been the same for 3 years. It worked fine and Duckdns still gets me to nextcloud so something is working. I'm definitely not going to give up. No port forwarding rules have changed. I don't want IPv6. My public IP takes me to the same generic NPM Congratulations page as every time I type in my subdomains from google domains. Something is getting through.  I don't know how it started. I'll continue to look for a solution.  Thanks.

Edited by DuneJeeper
ipv6 clarification
Link to comment

Hello, 

I recently switched from a netgear router, to UDM Pro, and its screwed up my Proxy setup and I can't figure out how.  One of the connections it screwed up is to Overseer.  

I just watched another video on it, and everything looks correct, I've attached the relevent pics.  If someone could look at it I would appreciate it.  

When I try to click on my site, it tells me the site is not safe, so I click to view it anyways then I get this.

 

This site can’t be reached

coltonoverseer.duckdns.org took too long to respond.

Try:

Checking the connection

Checking the proxy and the firewall

Running Windows Network Diagnostics

ERR_CONNECTION_TIMED_OUT

2022-12-05_10-31-08.jpg

2022-12-05_10-31-31.jpg

2022-12-05_10-32-01.jpg

2022-12-05_10-30-47.jpg

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.