severanced
-
Posts
137 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by severanced
-
-
I'm having the same issue which also just started. I've tried it in Firefox, Edge and Chrome and they all have similar behaviors. I can't see anything in the "Main" tab, Dashboard shows incomplete information and plugin's and docker never load.
EDIT: Using 6.11.5 Unraid
-
I upgraded to Paperless-NGX and I'm really happy with how it looks! Does anyone have an idea on if I did something wrong to get "not available" whenever I do a check for a new version?
-
Perhaps I need something explained to me about how Paperless-NGX works but I feel like I'm missing something.
When I scan a document I would like to have the newest documents I've added appear on my front page. my assumption is this is under the "Added" filter under documents, however I'll scan and add a document and have the filter set to "Last 7 Days" and documents I scan today won't show up. Is that filter set to the previous day and back 7 days from that?
-
52 minutes ago, strike said:
I can't see anything obvious in the logs aside form the ipv6 errors on the start of the log. But I don't think that has anything to with it. Make a backup of the privoxy folder in your appdata and delete it (or move it to a diffrent location), and restart the container. Did that make a difference?
From the looks of it that made the difference! It seems to connect and, from the looks of it, my other dockers can connect.
Thanks a ton that seems to have worked.
-
1
-
-
1 hour ago, strike said:
Did you change the privoxy port or something? Please post your template settings. And enable debug log while you're at it and post a new log. Does it connect to airvpn now and you can get to the webui?
Hi, here are my settings from the container, I enabled Debuging logs after I took this screenshot, and the debug logs too. And yes, I'm able to connect to AirVPN and log in to the WebGUI fine.
-
13 hours ago, strike said:
Don't mess with ports that was already there, they are there for a reason. You only need to change the host ports in the container template IF you have conflicting ports. If you don't then you don't need to touch them. So put it back to where it was and only change the host port if you need to. And yes, the incoming port you have from AirVpn does NOT go in the template but in the deluge settings in the webui.
Edit: If the port in the template you're referring to is this variable, then you have an old template like me and you can just delete it OR put the port that you're connecting to. But it won't make a difference anyway since this port get read from the ovpn file.
Thanks, it looks like that was my problem, DelugeVPN start up now, however I'm getting the same problems with getting Privoxy to start that I was having with PIA. Does anyone have any thoughts? I thought AIRVPN would be a bit more reliable.
Quote2023-01-03 09:55:20,096 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running2023-01-03 09:55:20,098 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...2023-01-03 09:55:32,195 DEBG 'watchdog-script' stdout output:
[warn] Wait for Privoxy process to start aborted, too many retries
[info] Showing output from command before exit...2023-01-03 09:56:03,373 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running2023-01-03 09:56:03,376 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...2023-01-03 09:56:15,474 DEBG 'watchdog-script' stdout output:
[warn] Wait for Privoxy process to start aborted, too many retries
[info] Showing output from command before exit...2023-01-03 09:57:16,682 DEBG 'watchdog-script' stdout output:
[info] Privoxy not running2023-01-03 09:57:16,685 DEBG 'watchdog-script' stdout output:
[info] Attempting to start Privoxy...2023-01-03 09:57:28,789 DEBG 'watchdog-script' stdout output:
[warn] Wait for Privoxy process to start aborted, too many retries
[info] Showing output from command before exit... -
43 minutes ago, strike said:
Where exactly did you do this? You're not supposed to put the forwarded port in the container settings. You put it in deluge settings for incoming port in the webui when the container has started.
I did put it in the container settings since the container won't start unless there are some ports added, am I just supposed to put some random numbers in there and then add the real ports in the Deluge UI?
-
Hi, I'm wondering if I can get some help, I'm trying to get Privoxy to work and in reading the forum I saw that PIA (what I was using) is being flaky so I replaced it with AirVPN. I set up a forwarded port and generated .crt/.key/.key and /.ovpn files and put them in openvpn (removing the PIA files) and when I change the ports to the ones I specified in AirVPN I get this error when I try to save the docker container:
docker: Error response from daemon: driver failed programming external connectivity on endpoint binhex-delugevpn (0ce07624958ca487d10d58fa71eadc16fe5c26b4d69ab7cbcb26546bcc3a61c9): Bind for 0.0.0.0:28312 failed: port is already allocated.
Goes without saying but I also can't start the container. Any ideas what I'm doing wrong?
-
Looks like the new update fixed it!
-
3 hours ago, RiDDiX said:
Maybe try to set permissions for appdata and your jdownloader2 folders.
I updated my container without any problems. Fluid as alwaysI just tried doing this, my permissions were already set to "read/write" throughout but I repushed the permissions for the jdownloader2 folder in appdata and no change, still ends with:
[cont-init ] 15-install-pkgs.sh: executing... [cont-init ] 15-install-pkgs.sh: terminated successfully. [cont-init ] 55-jdownloader2.sh: executing... [cont-init ] 55-jdownloader2.sh: terminated with error 1. -
I just updated Jdownloader and now I'm getting this error when I try to start it up, is this happening with anyone else?
[cont-init ] 10-certs.sh: terminated successfully. [cont-init ] 10-check-app-niceness.sh: executing... [cont-init ] 10-check-app-niceness.sh: terminated successfully. [cont-init ] 10-cjk-font.sh: executing... [cont-init ] 10-cjk-font.sh: terminated successfully. [cont-init ] 10-clean-logmonitor-states.sh: executing... [cont-init ] 10-clean-logmonitor-states.sh: terminated successfully. [cont-init ] 10-clean-tmp-dir.sh: executing... [cont-init ] 10-clean-tmp-dir.sh: terminated successfully. [cont-init ] 10-fontconfig-cache-dir.sh: executing... [cont-init ] 10-fontconfig-cache-dir.sh: terminated successfully. [cont-init ] 10-init-users.sh: executing... [cont-init ] 10-init-users.sh: terminated successfully. [cont-init ] 10-jwm.sh: executing... [cont-init ] 10-jwm.sh: terminated successfully. [cont-init ] 10-nginx.sh: executing... [cont-init ] 10-nginx.sh: terminated successfully. [cont-init ] 10-set-tmp-dir-perms.sh: executing... [cont-init ] 10-set-tmp-dir-perms.sh: terminated successfully. [cont-init ] 10-vnc-password.sh: executing... [cont-init ] 10-vnc-password.sh: terminated successfully. [cont-init ] 10-web-data.sh: executing... [cont-init ] 10-web-data.sh: terminated successfully. [cont-init ] 10-x11-unix.sh: executing... [cont-init ] 10-x11-unix.sh: terminated successfully. [cont-init ] 10-xdg-runtime-dir.sh: executing... [cont-init ] 10-xdg-runtime-dir.sh: terminated successfully. [cont-init ] 15-install-pkgs.sh: executing... [cont-init ] 15-install-pkgs.sh: terminated successfully. [cont-init ] 55-jdownloader2.sh: executing... [cont-init ] 55-jdownloader2.sh: terminated with error 1. [init ] container is starting... [cont-env ] loading container environment variables... [cont-env ] APP_NAME: loading... [cont-env ] DISPLAY: executing... [cont-env ] DISPLAY: terminated successfully. [cont-env ] DISPLAY: loading... [cont-env ] DOCKER_IMAGE_PLATFORM: loading... [cont-env ] DOCKER_IMAGE_VERSION: loading... [cont-env ] GTK_THEME: executing... [cont-env ] GTK_THEME: terminated successfully. [cont-env ] GTK_THEME: loading... [cont-env ] HOME: loading... [cont-env ] INSTALL_PACKAGES_INTERNAL: executing... [cont-env ] INSTALL_PACKAGES_INTERNAL: terminated successfully. [cont-env ] INSTALL_PACKAGES_INTERNAL: loading... [cont-env ] QT_STYLE_OVERRIDE: executing... [cont-env ] QT_STYLE_OVERRIDE: terminated successfully. [cont-env ] QT_STYLE_OVERRIDE: loading... [cont-env ] TAKE_CONFIG_OWNERSHIP: loading... [cont-env ] XDG_CACHE_HOME: loading... [cont-env ] XDG_CONFIG_HOME: loading... [cont-env ] XDG_DATA_HOME: loading... [cont-env ] XDG_RUNTIME_DIR: loading... [cont-env ] container environment variables initialized. [cont-secrets] loading container secrets... [cont-secrets] container secrets loaded. [cont-init ] executing container initialization scripts... [cont-init ] 10-certs.sh: executing... [cont-init ] 10-certs.sh: terminated successfully. [cont-init ] 10-check-app-niceness.sh: executing... [cont-init ] 10-check-app-niceness.sh: terminated successfully. [cont-init ] 10-cjk-font.sh: executing... [cont-init ] 10-cjk-font.sh: terminated successfully. [cont-init ] 10-clean-logmonitor-states.sh: executing... [cont-init ] 10-clean-logmonitor-states.sh: terminated successfully. [cont-init ] 10-clean-tmp-dir.sh: executing... [cont-init ] 10-clean-tmp-dir.sh: terminated successfully. [cont-init ] 10-fontconfig-cache-dir.sh: executing... [cont-init ] 10-fontconfig-cache-dir.sh: terminated successfully. [cont-init ] 10-init-users.sh: executing... [cont-init ] 10-init-users.sh: terminated successfully. [cont-init ] 10-jwm.sh: executing... [cont-init ] 10-jwm.sh: terminated successfully. [cont-init ] 10-nginx.sh: executing... [cont-init ] 10-nginx.sh: terminated successfully. [cont-init ] 10-set-tmp-dir-perms.sh: executing... [cont-init ] 10-set-tmp-dir-perms.sh: terminated successfully. [cont-init ] 10-vnc-password.sh: executing... [cont-init ] 10-vnc-password.sh: terminated successfully. [cont-init ] 10-web-data.sh: executing... [cont-init ] 10-web-data.sh: terminated successfully. [cont-init ] 10-x11-unix.sh: executing... [cont-init ] 10-x11-unix.sh: terminated successfully. [cont-init ] 10-xdg-runtime-dir.sh: executing... [cont-init ] 10-xdg-runtime-dir.sh: terminated successfully. [cont-init ] 15-install-pkgs.sh: executing... [cont-init ] 15-install-pkgs.sh: terminated successfully. [cont-init ] 55-jdownloader2.sh: executing... [cont-init ] 55-jdownloader2.sh: terminated with error 1. -
Hello, some time ago I was having huge issues with SMB slowness (I still am so I'm hoping the new upgrade will help). As per some recommendations I changed my SMB settings and added: "case sensitive = yes". With the new upgrade, I'm trying to get SMB back to a default state so I can see if I can get some better throughput out of it, but I'm worried about removing that setting. Any idea what might happen if I have any folders that have identical names but different cases in a directory? I've run "Fix common problems" and tried to clear out as many as possible, but I'm worried if one sneaks in there what it might do to the server once I remove that.
-
I tried starting up the Docker and it looks like it works, I also enabled log rotation so hopefully this won't happen again.
-
17 hours ago, trurl said:
Neither of your pools are full but you do have docker.img corruption.
Disable Docker in Settings then reboot so your logs are cleared.
Then go to User Shares page, click Compute All button, wait for the results, and post a screenshot. If you don't get full results after a few minutes refresh the page.
I hope this helps, it's still going through a parity check.
-
Thanks, I'm just waiting for it to compute, it's taking a very long time and on the reboot started another parity check so things are moving slowly.
-
Hello! I started getting messages that my cache drive at 93% and growing so I started my mover, but that didn't seem to fix anything. Eventually my docker seemed to fail and now won't start and my log is at 100%. I'm sure this has something to do with it but I'm not sure what I should do to fix it.
I've attached my diagnostics I hope that I've got something that can be fixed easily. Any help is appreciated!
Thanks
-
Hello,
I've been having issues with very slow SMB response on Unraid. Literally takes minutes to pull up large media folders. Some time ago I addressed this in an older version of Unraid which, at the time, was addressed by forcing unraid to SMB version 1. My understanding is that this was done by adding "case sensitive = yes" to the SMB Extras area in Settings as documented here.
I'm wondering if I need to force a newer version of SMB? I'm concern is, if I remove the "case sensitive = yes" from SMB Extras if that will cause some issues with my system? I'm concerned that i may have some folder somewhere that is named the same as another just with a different case.
This is my current SMB Extras config:
Quotecase sensitive = yes
#unassigned_devices_start
#Unassigned devices share includes
include = /tmp/unassigned.devices/smb-settings.conf
#unassigned_devices_end
#vfs_recycle_start
#Recycle bin configuration
[global]
syslog only = Yes
syslog = 0
logging = 0
log level = 0 vfs:0
#vfs_recycle_endAny advice for this? Would forcing a newer version of SMB help my situation? I've already got the Dynamix Cache Directories going which doesn't seem to help.
-
I'll happily delete the application and reinstall it since I've not done any configuration, but when I look at installing it, I don't see how to redirect where it installs to. Adding the host paths just adds access to the shares from what I've seen.
-
7 minutes ago, itimpi said:
Without knowing where the docker developer put those files then there is not much we can do to help you. In a Docker container the application is ‘installed’ by the container developer and you are downloading an already ‘installed’ application when you get a container.
So from the sound of it, until the developer reconfigures it to install for Unraid to AppData I'm SOL?
6 minutes ago, trurl said:If it was magically in appdata, do you know what files you want to edit?
I'm basically trying to write over the existing files with a current installation in order to retain a lot of settings
-
4 hours ago, trurl said:
They are an issue because
What exactly do you mean by this?
You didn't answer this question
What I mean is the config files that are installed with the Docker container, not paths that are explicitly defined, but the base install files, from what I'm told they are in the Docker IMG file but I don't know how to best get to them or how to set it up so it installs to Appdata instead of inside the docker IMG file if that's where they are.
So to answer the other question...No, I have no idea what the path is or even how to find it. That's what I've been asking.
I think this would be a lot easier if I could just set up that application to install to AppData instead.
-
38 minutes ago, trurl said:
Doesn't look like you configured any path mappings so the container only has access to internal storage (inside docker.img).
Do you know the path within the container of the files you need to modify?
Do you have any other working dockers?
So the path mappings aren't an issue, but that doesn't help my issue which is getting access to the Docker install/config files. Unless I'm missing something here.
-
25 minutes ago, trurl said:
The mappings are whatever you made them. Click on its icon, select edit, and post a screenshot.
I couldn't find anything in Edit settings that shows where its files are located.
-
5 hours ago, itimpi said:
The obvious question is what is the path inside the container to the files you want to be able to edit. If you know that then you could map this location to a folder under appdata.
it is also possible to open a shell inside the Docker if you want to make changes that way. The problem with that technique is that if the container ever gets an update then you lose any changes you make inside the container - hence the reason why config folders for containers are typically mapped to folders within the ‘appdata’ share so they are external to docker.img and thus survive updates.
I have no idea where anything is stored, this is part of the problem. I don't know if there's something in Docker in Unraid that can show me the mapping because I haven't found anything to direct me anywhere.
-
Sure, I'm trying to work with this application (https://hub.docker.com/r/suika/hydrus/) which is not in the App store but is available if the advanced options are enabled. I need to modify some files in the install of it but it installs, like from what you were saying, inside the docker img file.
Dashboard and Start unresponsive
in General Support
Posted
I'm also noticing that the Unraid Server plugin is acting strange and not able to connect, but I'm not able to delete it since I can't load the Plugins page.