Raspberry Pi 4 + nginx proxy manager

  • shadow_empire

    Hat den Titel des Themas von „Rasperry Pi 4 + nginx proxy manager“ zu „Raspberry Pi 4 + nginx proxy manager“ geändert.
  • Update (using the description https://nginxproxymanager.com/setup)


    (Mariadb is running on port 3306.)


    I am using this stack:


    production.json:

    Code
    {
      "database": {
        "engine": "mysql",
        "host": "192.168.1.243",
        "name": "npm",
        "user": "npm",
        "password": "npm",
        "port": 3306
      }
    }


    Starting the stack gets me these errors:


    Containers > npm_db_1:

    Code
    2020-06-15T08:45:35.406626347Z standard_init_linux.go:211: exec user process caused "exec format error",



    Containers > npm_app_1:

    Code
    WARNING: NODE_ENV value of 'production' did not match any deployment config file names.,
    [6/15/2020] [8:51:00 AM] [Global   ] › ✖  error     getaddrinfo ENOTFOUND db,
    [6/15/2020] [8:51:04 AM] [Global   ] › ✖  error     connect EHOSTUNREACH 172.20.0.3:3306,



    I am not sure with the volume mappings...


    Any help would be appreciated... - thx

  • I changed my compose to and it looks a little better now:




    /appdata/npm/data/logs/data/logs/error.log:

    Code
    2020/06/15 12:36:09 [error] 244#244: *71 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: nginxproxymanager, request: "GET /api/ HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "127.0.0.1:81"


    I get this error in portainer npm_app_1:

    Code
    parse error: Invalid numeric literal at line 1, column 7 NOT OK
    [6/15/2020] [12:42:57 PM] [Global   ] › ✖  error     ER_ACCESS_DENIED_ERROR: Access denied for user 'admin'@'172.17.0.1' (using password: YES)


    I get this error in portainer npm_db_1:

    Code
    standard_init_linux.go:211: exec user process caused "exec format error"



    I am also not sure if I have the correct MYSQL env variables and if my config.json is correct.

    Code
    {
    "database": {
    "engine": "mysql",
    "host": "192.168.1.243",
    "name": "npm",
    "user": "admin",
    "password": "*****",
    "port": 3306
    }
    }


    thx for the help...

  • yeah, overlooked this!

    db part is now up and running.


    still error in npm_app_1:

    Code
    parse error: Invalid numeric literal at line 1, column 7 NOT OK
    [6/15/2020] [1:14:42 PM] [Global   ] › ✖  error     ER_ACCESS_DENIED_ERROR: Access denied for user 'admin'@'172.17.0.1' (using password: YES)
  • I tried that as well, with this result:


    npm_db_1 log:

    Code
    2020-06-15 17:37:31 3638 [Warning] Access denied for user 'npm'@'172.20.0.3' (using password: YES)



    npm_app_1 log:

    Code
    [6/15/2020] [5:38:01 PM] [Global   ] › ✖  error     ER_ACCESS_DENIED_ERROR: Access denied for user 'npm'@'172.20.0.3' (using password: YES)


    Container health (npm_app_1):

    parse error: Invalid numeric literal at line 1, column 7 NOT OK



    compose file (I aslo tried with my MYSQL_ROOT_PASSWORD which I configured in Mariadb - same result):

  • here is my compose (just removed passwords):

  • Be carefull about indentations. Those seem to be removed while shadow_empire copy pasted his config.


    Greetings

    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

    • Offizieller Beitrag

    Be carefull about indentations.

    Good advise.


    If you have indent errors in Portainer/Stacks you will not be able to save the Stack. Portainer will highlight or otherwise point out the error (I don’t remember which) so it’s easy to correct. In a .yml file - if you have indent errors - you can save your work but when you run docker-compose up -d Terminal will return an error.

    System Backup Typo alert: Under the Linux section the command should be sudo umount /dev/sda1 NOT sudo unmount /dev/sda1

    Backup Data Disk to Backup Disk on Same Machine: In a Scheduled Job:rsync -av --delete /srv/dev-disk-by-uuid-f8814ed9-9a5c-4e1c-8830-426968c20ea3/ /srv/dev-disk-by-uuid-e67439d5-00a3-4942-bd5f-b84ab86aa850/ Don't forget trailing slashes, and BE CAREFUL. (HT: Getting Started with OMV5)

    Equipment - Thinkserver TS140, NanoPi M4 (v.1), Odroid XU4 (Using DietPi): PiHole

    Einmal editiert, zuletzt von Agricola ()

  • Code
    Hey everyone,


    I was searching the forums as I am having the exact same problem as shadow_empire had.

    And despite following the instructions here, I am still at a loss.


    So here is config.json file.


    Code
    {
      "database": {
        "engine": "mysql",
        "host": "db",
        "name": "npm",
        "user": "npm",
        "password": "npm",
        "port": 3306
      }
    }

    Portainer reports that the container is running however I when I check the logs I can see I am getting the below ouput for the DB.



    These are the lines that stuck out to me the most:


    Code
    2020-08-23 12:55:11 0 [ERROR] mysqld: Can't create/write to file '/var/tmp/ibXXXXXX' (Errcode: 13 "Permission denied")
    2020-08-23 12:55:11 0 [ERROR] InnoDB: Unable to create temporary file; errno: 13
    2020-08-23 12:55:11 0 [ERROR] mysqld: Can't create/write to file '/var/tmp/ibXXXXXX' (Errcode: 13 "Permission denied")


    It seems that there are permission errors. Which I can't seem to figure out.



    Here is my docker compose file. version: "2"


    This container is listed as unhealthy and gives me the following errors.



    I have tried using the fixes on here but they didn't work.

  • 2020-08-23 12:55:11 0 [ERROR] mysqld: Can't create/write to file '/var/lib/mysql/aria_log_control' (Errcode: 13 "Permission denied")


    volumes:
    - /mnt/sandisk500gb/dietpi_userdata/docker-data/nginx/config.json:/app/config/production.json


    EISDIR: illegal operation on a directory, read Error: Config file /app/config/production.json cannot be read. Error code is: EISDIR. Error message is: EISDIR: illegal operation on a directory, read

    Your config.json at /mnt/sandisk500gb/dietpi_userdata/docker-data/nginx/ is a folder, not a file. Remove it and add it again by using touch or nano.


    Greetings

    David

    "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

  • can some help me out too. Been at this for days

    this are my files an errors.\

    Thanks



    [8/25/2020] [4:15:43 PM] [Global ] › ✖ error connect ETIMEDOUT,

    [8/25/2020] [4:15:47 PM] [Global ] › ✖ error connect EHOSTUNREACH 172.23.0.2:3306,

    [8/25/2020] [4:15:48 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND db,

    [8/25/2020] [4:15:49 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND db,

    [8/25/2020] [4:15:50 PM] [Global ] › ✖ error getaddrinfo ENOTFOUND db,

  • "Well... lately this forum has become support for everything except omv" [...] "And is like someone is banning Google from their browsers"


    Only two things are infinite, the universe and human stupidity, and I'm not sure about the former.

    Upload Logfile via WebGUI/CLI
    #openmediavault on freenode IRC | German & English | GMT+1
    Absolutely no Support via PM!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!