TechKnowCase

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by TechKnowCase

  1. Hello!

     

    I'm having this super weird issue with the Ghost container. Strangely enough, this also happens with bitnami's Ghost container.

     

    Issue: When I start the container, it fails to connect to the DB because it connect using 'ghost'@'Ghost_testwebsite.br4' which is the right username, but it uses the container name.interface instead of the ip passed though "database__connection__host":

     

    Quote

    ERROR Access denied for user 'ghost'@'Ghost_testwebsite.br4' (using password: YES)

     

    Access denied for user 'ghost'@'Ghost_testwebsite.br4' (using password: YES)

     

    "Unknown database error"

     

    Error ID:
        500

     

    Error Code: 
        ER_ACCESS_DENIED_ERROR

     

    config:

     

    Quote

    docker create
      --name='Ghost_testwebsite'
      --net='br4'
      --ip='a.b.c.d'
      -e TZ="America/New_York"
      -e HOST_OS="Unraid"
      -e HOST_HOSTNAME="Unraid"
      -e HOST_CONTAINERNAME="Ghost_testwebsite"
      -e 'database__connection__host'='a.b.c.e'
      -e 'database__connection__user'='ghost'
      -e 'database__connection__password'='abcde'
      -e 'database__connection__database'='ghost'
      -e 'url'='https://example.ca'
      -e 'mail__transport'='SMTP'
      -e 'mail__options__service'='Mailgun'
      -e 'mail__options__auth__user'=''
      -e 'mail__options__auth__pass'=''
      -e 'PUID'='99'
      -e 'PGID'='100'
      -e 'database__client'='mysql'
      -e 'TCP_PORT_2368'='2368'
      -e 'NODE_ENV'='production'
      -l net.unraid.docker.managed=dockerman
      -l net.unraid.docker.icon='https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/images/Ghost.png'
      -v '/mnt/user/appdata/ghost/':'/var/lib/ghost/content':'rw' 'ghost'

    8848e7c6ce7f735927bf53997bab9c3461a8e789d4bb7c896b18023bae00f0c4

    The command finished successfully!

     

    Also, I tried to add "PUID" & "PGID" arguments to troubleshoot why the container is trying to write as the wrong user:

    Quote

    root@Unraid:/mnt/user/appdata/ghost# ls -la
    total 0
    drwxrwxrwx+ 1 techknowcase users  96 Jan  5 01:35 ./
    drwxrwxrwx  1 nobody       users 852 Oct 23 10:49 ../
    drwxr-x---+ 1 techknowcase users   0 Jan  2 13:28 apps/
    drwxr-x---+ 1 techknowcase users   0 Jan  2 13:28 data/
    drwxr-x---+ 1 techknowcase users   0 Jan  2 13:28 files/
    drwxr-x---+ 1 techknowcase users   0 Jan  2 13:28 images/
    drwxr-x---+ 1 techknowcase users 140 Jan  5 01:35 logs/
    drwxr-x---+ 1 techknowcase users   0 Jan  2 13:28 media/
    drwxr-x---+ 1 techknowcase users   0 Jan  2 13:28 public/
    drwxr-x---+ 1 techknowcase users   0 Jan  2 13:28 settings/
    drwxr-xr-x+ 1 techknowcase users  12 Jan  2 13:29 themes/

     

     

    Granted, techknowcase is my username on a few website on the internet, but never that username is passthough to the container. I'm not sure how Ghost was able to get that username somehow... if I reset the permissions to noody:users and launch the container again, it change it back to techknowcase:1000 when it boots. Even when I delete the ghost folder and everything in it.

     

    Thanks in advance!

  2. Hello all,

     

    I'm having some issues accessing the unraid webgui. I had issues before where this would happen, because of my ssl cert. I've come to the habbit of running the nginx command to see it's status (if I need to modify the /etc/nginx/conf.d/emhttp-servers.conf file).

     

    Now, I simply can't access the gui anymore, since that file is empty (0B). I'm not too sure where to look and what I can try next to throubleshoot the issue.

     

    Just before this, I had a warning that my cache drive was full. I shut down my deluge container to prevent data from being written to the cache, I ran mover and then set the share's cache setting to No to prevent this being an issue in the future. 

    At that point, I had issues where none of my containers could run (error 403). I told myself it might be because the cache was full. Nothing a good old reboot can't fix, right?

     

    That's where I am now. I can connect to the webgui, but I have access to SSH, my VMs are working, the dockers are still not functioning. the shares are also mounted (/mnt/user/...). 

     

    I have unraid V6.9.2, with the following plugins installed:

    Quote

    NerdPack/                   dynamix.apcupsd/         recycle.bin/
    NerdPack.plg                dynamix.cache.dirs/      recycle.bin.plg
    apache/                     dynamix.cache.dirs.plg   speedtest/
    ca.turbo/                   dynamix.my.servers/      statistics.sender/
    ca.turbo.plg                dynamix.ssd.trim/        statistics.sender.plg
    ca.update.applications/     dynamix.ssd.trim.plg     tips.and.tweaks/
    ca.update.applications.plg  dynamix.vm.manager/      tips.and.tweaks.plg
    community.applications/     fix.common.problems/     unassigned.devices/
    community.applications.plg  fix.common.problems.plg  unassigned.devices-plus/
    controlr/                   nut/                     unassigned.devices-plus.plg
    controlr.plg                nut.plg                  unassigned.devices.plg
    dockerMan/                  preclear.disk/           user.scripts/
    dynamix/                    preclear.disk.plg        user.scripts.plg

    I have the following Nerdpack packages:

    Quote

    nc-1.10-x86_64-1.txz                        python-pip-21.2.3-x86_64-1.txz
    ncurses-terminfo-6.1.20191130-x86_64-1.txz  python3-3.9.0-x86_64-1.txz
    netcat-openbsd-1.105-x86_64-2.tgz           tmux-3.1.0-x86_64-1.txz
    utempter-1.1.6.20191231-x86_64-3.txz
     

    I've attached the logs to this post.

     

    Restarting into safe mode does not fix the issue.

     

    Thanks for the help!

     

     

    thevault-diagnostics-20211003-1335.zip