nginx issue

[alexbonazzi]

I have TrueNAS Scale 22.12.3.3 and I reinstalled nginx 2.10.4_1.0.15 and put data and configuration files in a Host Folder (i.e. /mnt/disk1/disk2/nginx). when I start nginx is stuck in deploying and never come online. Anyone can suggest how to solve ?

 

[sretalla]

I reinstalled nginx 2.10.4_1.0.15

If that's a reinstall, what was installed before?

How did you install it? TrueCharts? Launch Docker Image?

 

[alexbonazzi]

It stops deploying 1 month ago.
I tried reinstalling official end truecharts apps with same result.
Now I reinstalled witout using host path but nothing changes.
if I launch from pod shell nginx this is result.

"nginx: [emerg] open() "/etc/nginx/conf.d/include/resolvers.conf" failed (2: No such file or directory) in /etc/nginx/nginx.conf:52"

 

[sretalla]

/etc/nginx/nginx.conf:52

So it appears line 52 of the config file points to a file (/etc/nginx/conf.d/include/resolvers.conf) which doesn't exist...

I don't think I see that same error, but the way forward would seem to be to remove that line from that file.

 

[sretalla]

Also, you mean nginx proxy manager, right?

 

[alexbonazzi]

I can't find any editor in pod how can

Also, you mean nginx proxy manager, right?

yes

 

[alexbonazzi]

So it appears line 52 of the config file points to a file (/etc/nginx/conf.d/include/resolvers.conf) which doesn't exist...

I don't think I see that same error, but the way forward would seem to be to remove that line from that file.

I can't find any editor in pod how to have one ? and how to make this change permanent ?

 

[sretalla]

I can't find any editor in pod how to have one ? and how to make this change permanent ?

I would start by creating an empty file in the expected location instead...

use

touch /etc/nginx/conf.d/include/resolvers.conf

Making it permanent is a whole different proposition as I haven't yet worked out why yours would be broken and mine isn't... perhaps that file is automatically created based on some DNS settings on the host.

 

[alexbonazzi]

I would start by creating an empty file in the expected location instead...

use

touch /etc/nginx/conf.d/include/resolvers.conf

Making it permanent is a whole different proposition as I haven't yet worked out why yours would be broken and mine isn't... perhaps that file is automatically created based on some DNS settings on the host.

nginx starts now thanks.
At login I got bad gateway now

 

[alexbonazzi]

I would start by creating an empty file in the expected location instead...

use

touch /etc/nginx/conf.d/include/resolvers.conf

Making it permanent is a whole different proposition as I haven't yet worked out why yours would be broken and mine isn't... perhaps that file is automatically created based on some DNS settings on the host.

I added a resolver directive and now I got this.

nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/npm-3/fullchain.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/npm-3/fullchain.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

 

[sretalla]

It occurs to me that you may benefit from doing this:

SOLVED - K3s: default route configured, but error "not present on any cidr used by the system"

Hi. After setting the default route for my k3s, I still get the following error : kubernetes.route_v4_gateway: Specified value is not present on any network cidr in use by the system However, the k3s gateway is set to 192.168.1.1, and I have a NIC with address 192.168.1.21/24. I've had this...

www.truenas.com

 

[alexbonazzi]

Solved certificate. Now at login I get bad gateway and took time many mintues to be active. Then when I add a host I get internal error.