TechKnowCase
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by TechKnowCase
-
-
Update: moving the Nerdpack folder away from /boot/config/plugins/ fixed the issue. I'm currently testing which package is causing this.
-
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:
QuoteNerdPack/ 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.plgI have the following Nerdpack packages:
Quotenc-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!
-
How did you guys managed to make it work? I followed Z3RO's instructions. This is what the page looks like:
Any idea?
[Support] cheesemarathons repo
in Docker Containers
Posted · Edited by TechKnowCase
misspelled
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":
config:
Also, I tried to add "PUID" & "PGID" arguments to troubleshoot why the container is trying to write as the wrong user:
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!