A major sucky day... lost access to nginx proxy manager

Currently reading
A major sucky day... lost access to nginx proxy manager

4,027
1,378
NAS
DS4l8play, DS202j, DS3623xs+, DSM 7.3.3-25847
How do these things happen? I have had npm docker container running on rpi and all seems well. When I went to log in to add a new RP entry, I get "bad gateway".

After updating images, deleting and re-adding the stack, and trying 3 different browsers, all with the same result, I'm flummoxed.

I suppose the next step is to recall all the forwards by memory (I must have screenshotted this) and return them to Synology... then maybe wipe the rpi database and try again. I haven't updated this system for quite some time. So "nothing changed" (yea, we've all heard that qualifier before).

Appreciate any wise words from the more experienced.

😬
 
btw, check the image "lastest" version installed - to be sure what exact version is there:

Bash:
docker images | grep proxy
copy Repo name or Image ID

Bash:
docker image inspect <Repo name or Image ID> | grep NPM_BUILD_VERSION
example: docker image inspect 47505d315fc1 | grep NPM_BUILD_VERSION

post it here

Note:
there is a standardized approach to checking the image version, which doesn't work for this author's approach to keeping the standards :rolleyes: :
Bash:
docker image inspect --format '{{json .}}' "<Image-ID>" | jq -r '. | {Labels: .org.opencontainers.image.version}'
I have prepared a functional command for this image (above). It will not work for you with another image.
 
Upvote 0
@Telos
I'm missing an answer if you did one of my recommendations in #23 related to Py in RPi:
Bash:
sudo apt install python3-dev
because your NPM log contains errors related.

Deep dive:

Following the long read on the official GitHub site, there is an issue with "python cryptography library" used for RPi and the problem of NPM with "502" persist from 2.9.15 to 2.9.18 (the reason why I asked for the version value above).

try to use tuned docker-compose for this RPi issue:
two new lines:
single in ENV
single in command

YAML:
version: "3"
services:
  app:
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      # These ports are in format <host-port>:<container-port>
      - '80:80' # Public HTTP Port
      - '443:443' # Public HTTPS Port
      - '81:81' # Admin Web Port
      # Add any other Stream port you want to expose
      # - '21:21' # FTP
    environment:
      DB_MYSQL_HOST: "name of the mysql host"
      DB_MYSQL_PORT: port defined in the db, instead 3306
      DB_MYSQL_USER: "Schema user"
      DB_MYSQL_PASSWORD: "user psw"
      DB_MYSQL_NAME: "Schema name"
      # here is aborted Rust dependencies installation
      CRYPTOGRAPHY_DONT_BUILD_RUST=1
    # here is installation of older Py cryptography package, which is fine
    command: pip install cryptography==3.4.6

    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt
      - ./config.json:/app/config/production.json
 
Upvote 0
Last edited:
Recommendation:
- stop the current stack
- try to create a new mysql container
- use mysql official docker image instead the alpine custom mariadb (defined in the NPM)
I didn't get too far with this ...

Tried... docker-compose initially, via Portainer
Code:
---
version: '3.4'
services:
  db:
    image: mysql
    container name: mysql-test
    restart: unless-stopped
    ports:
      - 3307:3306
    environment:
      MYSQL DATABASE: 'npm'
      MYSQL USER: 'npm'
      MYSQL PASSWORD: 'npm'
      MYSQL_ROOT_PASSWORD: 'rpwd'
    volumes:
      - ./mysql/data/db:/var/lib/mysql
Initially it complained that “container name” was not supported, so I commented it out and it failed with...

no matching manifest for linux/arm/v7 in the manifest list entries

That's a deal-killer for the RPi, I presume.

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
EDIT1:

I'm confused.
I launched the MySQL template that was offered in Portainer, and a container was successfully created (although it logged several “exec /entrypoint.sh: exec format error” errors). I'm not sure what to do with that.

It shows as "mysql/mysql-server:5.7
 
Upvote 0
I’m not a familiar with RPi, but as far as I know, Ubuntu runs there without any problems
So what about this case:
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
Upvote 0
I didn't get too far with this ...

Tried... docker-compose initially, via Portainer
Code:
---
version: '3.4'
services:
  db:
    image: mysql
    container name: mysql-test
    restart: unless-stopped
    ports:
      - 3307:3306
    environment:
      MYSQL DATABASE: 'npm'
      MYSQL USER: 'npm'
      MYSQL PASSWORD: 'npm'
      MYSQL_ROOT_PASSWORD: 'rpwd'
    volumes:
      - ./mysql/data/db:/var/lib/mysql
Initially it complained that “container name” was not supported, so I commented it out and it failed with...

no matching manifest for linux/arm/v7 in the manifest list entries

That's a deal-killer for the RPi, I presume.

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
EDIT1:

I'm confused.
I launched the MySQL template that was offered in Portainer, and a container was successfully created (although it logged several “exec /entrypoint.sh: exec format error” errors). I'm not sure what to do with that.

It shows as "mysql/mysql-server:5.7

I run multiple mysql instances for testing to production.

Hope this will help, runs fine for me with 0 issues

YAML:
version: '3.1'

services:

  db:
    image: mysql:latest
    network_mode: bridge
    command: --authentication_policy=mysql_native_password
    container_name: mysql8
    restart: always
    ports:
      - 3306:3306
    volumes:
      - /volume1/docker/mysql8:/var/lib/mysql
    environment:
      MYSQL_ROOT_PASSWORD: root_pass
 
Upvote 0
So what about this case
That's a different OS. I'm on Raspbian, 32-bit, so ARM7. When I set up the RPi 32-bit was stable, and I went with that. It's possible to "flip" the kernel to 64-bit (OS remains 32-bit, of course), and that has its own batch of side effects.

I may give that a shot, which might trick Docker into pulling ARM8 images (MySQL is not available in ARM7). But the shore seems much further away, and the waves are getting choppy, and the shoal more intimidating... so I may have to grab another RPi, or work with what I have.
 
Upvote 0

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Synology fixed it for me, apparently Windows V below 10 need an adjustment to communicate with Synology...
Replies
7
Views
892
This is crazy... and they are saying this was all due to a Plex media RCE exploit Plex media server seen...
Replies
2
Views
1,572
Replies
6
Views
1,471
The IP address for the router connection (LAN 1) was 192.168.xxx.xx while the 10GbE (LAN 3) IP address is...
Replies
10
Views
2,349
Yesterday I've updated some packages, on my DS918+ (running DSM 7.1), assuming that included the nginx...
Replies
0
Views
1,391

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top