[Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot

[Cesar Mora]

Thanks for the reply! Yes, as I included in the previous message:

root at spce:/etc/nginx/sites-enabled# ls
ngcp-panel_admin_api  ngcp-panel_csc  ngcp-panel_system_api  nginx-status

There is no file or directory called nginx in /etc/nginx/sites-enabled/. What you see there is what is in there. Inside  /etc/nginx/sites-enabled are:

 gcp-panel_admin_api  ngcp-panel_csc  ngcp-panel_system_api  nginx-status

And the nginx-status file in there contains what I posted earlier.

I also want to add, I tried a clean install on a VirtualBox for testing, and I was able to get a full clean install with no nginx problems. The difference is that my physical server has 2 NICs and after ‘ngcp-initial-config’ you cannot access web or anything, and I had to do ngcp-network to move the listening services over to neth0, but the virtualbox machine with only one eth0 NIC did not need this step, and already had the listening port's at eth0 and working out of the box. So my install seems to get messed up after ngcp-network for being a physical server, and not a VM with 1 NIC with default eth0 name.

Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Michael Prokop via Spce-user <spce-user at lists.sipwise.com>
Sent: Monday, January 27, 2025 4:05:55 AM
To: spce-user at lists.sipwise.com <spce-user at lists.sipwise.com>
Subject: Re: [Spce-user] [EXTERNAL] Re: nginx and prometheus-nginx-exporter fail to load after reboot

Hi,

* Cesar Mora [Fri Jan 24, 2025 at 03:16:22PM -0400]:

> I haven’t modified any of these files. All I can think of is that something gets messed up in there when I perform the initial "ngcp-network” to define neth0 as the main interface (my server has 2 NICs) with:

[...]

> Anyways… The files under /etc/nginx/sites-enabled/ look as:
>
> root at spce:/etc/nginx/sites-enabled# ls
> ngcp-panel_admin_api  ngcp-panel_csc  ngcp-panel_system_api  nginx-status
>
> And inside nginx-status is:
>
> server {
>        listen localhost:8081;
>        #server_name  localhost;
>
>        location /nginx_status {
>                stub_status on;
>                access_log off;
>                allow 127.0.0.1;
>                allow ::1;
>                deny all;
>        }
> }

This looks ok, but as already written:

> > On Jan 22, 2025, at 11:27 AM, Michael Prokop via Spce-user <spce-user at lists.sipwise.com> wrote:

> > What do you have inside /etc/nginx/sites-enabled/nginx and what are
> > the files looking like, where port 8081 is referred to? (One of them
> > should be /etc/nginx/sites-available/nginx-status)

You seem to have another file which uses port 8081.

regards
-mika-

--
Spce-user mailing list
Spce-user at lists.sipwise.com
http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20250127/0705a08d/attachment-0001.htm>