NPM gets internal error when running in an LXC (Proxmox)

[NickRO19]

After installing NPM in Docker, everything works fine until I try to get a SSL cert.

Privileged container with ports 80 and 443 forwarded to the LXC.
Used the following script to install.
docker run -d
--name=nginx-proxy-manager
-p 81:8181
-p 80:8080
-p 443:4443
-v /docker/appdata/nginx-proxy-manager:/config:rw
jlesage/nginx-proxy-manager

I get an internal error when requesting the SSL cert from Let's Encrypt. It also may just hang sometimes when trying to update a failed request.

Using Ubuntu 18.04 standard template LXC inside Proxmox 6.2-4

[Oujiii]

Hey! You didn't mention me so I had no idea you had opened this.

Is there any reason why you are not using jc21's container? I know you said it works on a VM, but I'm just wondering. Also, which db are you using for it?

[dash74]

I can confirm that jc21's works in proxmox without any issue. Although I am using it in an unprivileged container. Since docker doesn't usually play well in a privileged container by default.

[NickRO19]

Hey! You didn't mention me so I had no idea you had opened this.

Is there any reason why you are not using jc21's container? I know you said it works on a VM, but I'm just wondering. Also, which db are you using for it?

Sorry, kinda new to github...

jc21's I have the same exact issue. Here is my compose file
version: "3"
services:
app:
image: jc21/nginx-proxy-manager:2
restart: always
ports:
# Public HTTP Port:
- '80:80'
# Public HTTPS Port:
- '443:443'
# Admin Web Port:
- '81:81'
environment:
# Uncomment this if IPv6 is not enabled on your host
# DISABLE_IPV6: 'true'
volumes:
# Make sure this config.json file exists as per instructions above:
- ./config.json:/app/config/production.json
- ./data:/data
- ./letsencrypt:/etc/letsencrypt
depends_on:
- db
db:
image: jc21/mariadb-aria:latest
restart: always
environment:
MYSQL_ROOT_PASSWORD: 'npm'
MYSQL_DATABASE: 'npm'
MYSQL_USER: 'npm'
MYSQL_PASSWORD: 'npm'
volumes:
- ./data/mysql:/var/lib/mysql

And here is the config.json file
{
"database": {
"engine": "mysql",
"host": "db",
"name": "npm",
"user": "npm",
"password": "npm",
"port": 3306
}
}

I changed the passwords obviously... but i made sure they match up

[NickRO19]

I can confirm that jc21's works in proxmox without any issue. Although I am using it in an unprivileged container. Since docker doesn't usually play well in a privileged container by default.

Do you mean the other way around? I always use a privileged container, whenever I use unprivileged docker has issues

[dash74]

I can confirm that jc21's works in proxmox without any issue. Although I am using it in an unprivileged container. Since docker doesn't usually play well in a privileged container by default.

Do you mean the other way around? I always use a privileged container, whenever I use unprivileged docker has issues

Nope... Here is a screenshot of my lxc container. It's an unprivileged container. I actually had issues installing docker in a privileged container. When I attempted it. I'm using Ubuntu 20.04 standard template. I don't know if that would a difference. You do have too make sure you have nesting and keyctl checked to make it work for unprivileged.

[NickRO19]

Interesting... what version of Ubuntu server are you using?

…

-------- Original Message --------

On Aug 30, 2020, 12:22, dash74 wrote: >> I can confirm that jc21's works in proxmox without any issue. Although I am using it in an unprivileged container. Since docker doesn't usually play well in a privileged container by default. > > Do you mean the other way around? I always use a privileged container, whenever I use unprivileged docker has issues Nope... Here is a screenshot of my lxc container. It's an unprivileged container. [image](https://user-images.githubusercontent.com/28696570/91664131-3cea6680-eabb-11ea-9ddf-67ee4cc21bbe.png) — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#579 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ALYVWDUOLNOB6WSMOWIC5BDSDJ4EJANCNFSM4QKEOGOQ).

[NickRO19]

I tried the unprivileged container using Ubuntu 18.04. Still get the same internal error

…

-------- Original Message --------

On Aug 30, 2020, 12:22, dash74 wrote: >> I can confirm that jc21's works in proxmox without any issue. Although I am using it in an unprivileged container. Since docker doesn't usually play well in a privileged container by default. > > Do you mean the other way around? I always use a privileged container, whenever I use unprivileged docker has issues Nope... Here is a screenshot of my lxc container. It's an unprivileged container. [image](https://user-images.githubusercontent.com/28696570/91664131-3cea6680-eabb-11ea-9ddf-67ee4cc21bbe.png) — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#579 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ALYVWDUOLNOB6WSMOWIC5BDSDJ4EJANCNFSM4QKEOGOQ).

[dash74]

I'm using Ubuntu 20.04 standard template. As I mentioned, you do have to make sure nesting and keyctl are checked for docker too work. In an unprivileged container. I just tried installing docker again in a privileged container. Both 18.04 and 20.04. I get docker: Error response from daemon: error creating aufs mount. When attempting too run the sudo docker run hello-world. I'm using the repository install method. It appears it has to do with the storage device. driver. Installing docker in an unprivileged container just works for me, without issue.

What version of Proxmox are you using? I am using 6.2-11.

Interesting... what version of Ubuntu server are you using?
…
-------- Original Message --------
On Aug 30, 2020, 12:22, dash74 wrote: >> I can confirm that jc21's works in proxmox without any issue. Although I am using it in an unprivileged container. Since docker doesn't usually play well in a privileged container by default. > > Do you mean the other way around? I always use a privileged container, whenever I use unprivileged docker has issues Nope... Here is a screenshot of my lxc container. It's an unprivileged container. image — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#579 (comment)), or unsubscribe.

[NickRO19]

Ok, so I do not get that error when installing in a privileged container. Regardless its working in a unprivileged just fine. I do have those options checked and its running. As always though, I still get the internal error when requesting a SSL cert from Lets encrypt

…

-------- Original Message --------

On Aug 30, 2020, 14:13, dash74 wrote: I'm using Ubuntu 20.04 standard template. As I mentioned, you do have to make sure nesting and keyctl are checked for docker too work. In an unprivileged container. I just tried installing docker again in a privileged container. Both 18.04 and 20.04. I get docker: Error response from daemon: error creating aufs mount. When attempting too run the sudo docker run hello-world. I'm using the repository install method. It appears it has to do with the storage device. driver. Installing docker in an unprivileged container just works for me, without issue. > Interesting... what version of Ubuntu server are you using? > […](#) > -------- Original Message -------- > On Aug 30, 2020, 12:22, dash74 wrote: >> I can confirm that jc21's works in proxmox without any issue. Although I am using it in an unprivileged container. Since docker doesn't usually play well in a privileged container by default. > > Do you mean the other way around? I always use a privileged container, whenever I use unprivileged docker has issues Nope... Here is a screenshot of my lxc container. It's an unprivileged container. [image](https://user-images.githubusercontent.com/28696570/91664131-3cea6680-eabb-11ea-9ddf-67ee4cc21bbe.png) — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub]([#579 (comment)](#579 (comment))), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ALYVWDUOLNOB6WSMOWIC5BDSDJ4EJANCNFSM4QKEOGOQ). — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#579 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ALYVWDQ4YGVOGZR7EDTH6SDSDKJEJANCNFSM4QKEOGOQ).

[dash74]

Have you looked at the letsencrypt-requests.log? Do any of the logs provide more info?

Ok, so I do not get that error when installing in a privileged container. Regardless its working in a unprivileged just fine. I do have those options checked and its running. As always though, I still get the internal error when requesting a SSL cert from Lets encrypt
…
-------- Original Message --------
On Aug 30, 2020, 14:13, dash74 wrote: I'm using Ubuntu 20.04 standard template. As I mentioned, you do have to make sure nesting and keyctl are checked for docker too work. In an unprivileged container. I just tried installing docker again in a privileged container. Both 18.04 and 20.04. I get docker: Error response from daemon: error creating aufs mount. When attempting too run the sudo docker run hello-world. I'm using the repository install method. It appears it has to do with the storage device. driver. Installing docker in an unprivileged container just works for me, without issue. > Interesting... what version of Ubuntu server are you using? > … > -------- Original Message -------- > On Aug 30, 2020, 12:22, dash74 wrote: >> I can confirm that jc21's works in proxmox without any issue. Although I am using it in an unprivileged container. Since docker doesn't usually play well in a privileged container by default. > > Do you mean the other way around? I always use a privileged container, whenever I use unprivileged docker has issues Nope... Here is a screenshot of my lxc container. It's an unprivileged container. image — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub]([#579 (comment)](#579 (comment))), or unsubscribe. — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#579 (comment)), or unsubscribe.

[NickRO19]

I'm pretty new to this so excuse my lack of knowledge. Where can I find those logs?

…

-------- Original Message --------

On Aug 30, 2020, 14:48, dash74 wrote: Have you looked at the letsencrypt-requests.log? Do any of the logs provide more info? > Ok, so I do not get that error when installing in a privileged container. Regardless its working in a unprivileged just fine. I do have those options checked and its running. As always though, I still get the internal error when requesting a SSL cert from Lets encrypt > […](#) > -------- Original Message -------- > On Aug 30, 2020, 14:13, dash74 wrote: I'm using Ubuntu 20.04 standard template. As I mentioned, you do have to make sure nesting and keyctl are checked for docker too work. In an unprivileged container. I just tried installing docker again in a privileged container. Both 18.04 and 20.04. I get docker: Error response from daemon: error creating aufs mount. When attempting too run the sudo docker run hello-world. I'm using the repository install method. It appears it has to do with the storage device. driver. Installing docker in an unprivileged container just works for me, without issue. > Interesting... what version of Ubuntu server are you using? > […](#) > -------- Original Message -------- > On Aug 30, 2020, 12:22, dash74 wrote: >> I can confirm that jc21's works in proxmox without any issue. Although I am using it in an unprivileged container. Since docker doesn't usually play well in a privileged container by default. > > Do you mean the other way around? I always use a privileged container, whenever I use unprivileged docker has issues Nope... Here is a screenshot of my lxc container. It's an unprivileged container. [image](https://user-images.githubusercontent.com/28696570/91664131-3cea6680-eabb-11ea-9ddf-67ee4cc21bbe.png) — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub]([[#579](#579) (comment)]([#579 (comment)](#579 (comment)))), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ALYVWDUOLNOB6WSMOWIC5BDSDJ4EJANCNFSM4QKEOGOQ). — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub]([#579 (comment)](#579 (comment))), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ALYVWDQ4YGVOGZR7EDTH6SDSDKJEJANCNFSM4QKEOGOQ). — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#579 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ALYVWDUIMGC2KCITGWBLBILSDKNHNANCNFSM4QKEOGOQ).

[dash74]

There should be a folder /data/logs. It would be created in the directory you're running the command line or yml file. You should see something like this.

I'm pretty new to this so excuse my lack of knowledge. Where can I find those logs?
…
-------- Original Message --------
On Aug 30, 2020, 14:48, dash74 wrote: Have you looked at the letsencrypt-requests.log? Do any of the logs provide more info? > Ok, so I do not get that error when installing in a privileged container. Regardless its working in a unprivileged just fine. I do have those options checked and its running. As always though, I still get the internal error when requesting a SSL cert from Lets encrypt > … > -------- Original Message -------- > On Aug 30, 2020, 14:13, dash74 wrote: I'm using Ubuntu 20.04 standard template. As I mentioned, you do have to make sure nesting and keyctl are checked for docker too work. In an unprivileged container. I just tried installing docker again in a privileged container. Both 18.04 and 20.04. I get docker: Error response from daemon: error creating aufs mount. When attempting too run the sudo docker run hello-world. I'm using the repository install method. It appears it has to do with the storage device. driver. Installing docker in an unprivileged container just works for me, without issue. > Interesting... what version of Ubuntu server are you using? > … > -------- Original Message -------- > On Aug 30, 2020, 12:22, dash74 wrote: >> I can confirm that jc21's works in proxmox without any issue. Although I am using it in an unprivileged container. Since docker doesn't usually play well in a privileged container by default. > > Do you mean the other way around? I always use a privileged container, whenever I use unprivileged docker has issues Nope... Here is a screenshot of my lxc container. It's an unprivileged container. image — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub]([#579 (comment)]([#579 (comment)](#579 (comment)))), or unsubscribe. — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub]([#579 (comment)](#579 (comment))), or unsubscribe. — You are receiving this because you authored the thread. Reply to this email directly, [view it on GitHub](#579 (comment)), or unsubscribe.

[NickRO19]

I am so sorry for delaying in solving my own issue. Family health problems...
Just to update I have recently switch to trying this on a VM. I always get the same internal error when trying to get a lets encrypt cert.
I have double checked my dns settings, my ports are open, I can reach my admin page and even see the "Congrats" page when going to my website using regular http.
Whenever i try to get a cert still get the internal error.
Also @dash74 I cannot find that folder "data". Where would it be from the "/" directory? Sorry I'm kind of new to this proxy stuff.

[github-actions]

Issue is now considered stale. If you want to keep it open, please comment 👍