dharrah Posted October 7, 2020 Share Posted October 7, 2020 (edited) Just deployed the CrushFTP9 app and turned off my stuckless/crushftp I had previously had the stuckless app behind SWAG and working just fine. I set my ports the same and it is on the SWAG custom network When I first started CrushFTP9 up, I bounced SWAG and everything came up fine. All my other SSL dockers work except for the CrushFTP9 - all I get is "502 Bad Gateway" Here is my conf file: server { listen 443 ssl; server_name transport.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; proxy_max_temp_file_size 2048m; proxy_pass https://<unraidIP>:9443; } } server { listen 9021; server_name transport.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; proxy_max_temp_file_size 2048m; proxy_pass https://<unraidIP>:9021; } } I feel like I am missing something dumb/small.....but can't seem to find it. Any ideas? Edited October 7, 2020 by dharrah Quote Link to comment
Roxedus Posted October 7, 2020 Author Share Posted October 7, 2020 @CorneliousJD Unfortunately doing a switch isn't that easy, template wise. The best approach would be to create a separate template for the new image to not break existing installs, and have fix common problems tell users to switch. I will do the first part now. Quote Link to comment
Roxedus Posted October 7, 2020 Author Share Posted October 7, 2020 13 hours ago, dharrah said: Just deployed the CrushFTP9 app and turned off my stuckless/crushftp I had previously had the stuckless app behind SWAG and working just fine. I set my ports the same and it is on the SWAG custom network When I first started CrushFTP9 up, I bounced SWAG and everything came up fine. All my other SSL dockers work except for the CrushFTP9 - all I get is "502 Bad Gateway" Here is my conf file: server { listen 443 ssl; server_name transport.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; proxy_max_temp_file_size 2048m; proxy_pass https://<unraidIP>:9443; } } server { listen 9021; server_name transport.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; proxy_max_temp_file_size 2048m; proxy_pass https://<unraidIP>:9021; } } I feel like I am missing something dumb/small.....but can't seem to find it. Any ideas? 502 means nginx cant talk to the container. Quote Link to comment
CorneliousJD Posted October 7, 2020 Share Posted October 7, 2020 2 hours ago, Roxedus said: @CorneliousJD Unfortunately doing a switch isn't that easy, template wise. The best approach would be to create a separate template for the new image to not break existing installs, and have fix common problems tell users to switch. I will do the first part now. I thought that might be the case actually after I posted it and thought about it 5 minutes later Thanks for handling that. If you need anything from me just @ me. thanks! Quote Link to comment
dharrah Posted October 7, 2020 Share Posted October 7, 2020 (edited) On 10/7/2020 at 11:07 AM, Roxedus said: 502 means nginx cant talk to the container. This is fixed. I had to ultimately point my conf to http and port 9090 in SWAG: server { listen 443 ssl; server_name transport.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; proxy_max_temp_file_size 2048m; set $upstream_app newcrushftp; set $upstream_port 9090; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } Edited October 9, 2020 by dharrah changed port to 9090 Quote Link to comment
Nanobug Posted October 16, 2020 Share Posted October 16, 2020 Hello, I can't figure out how to set up XBackBone. I looked at the Github link and the XBacBone documentation. I tried Googling for a guide to it, but when I try to access it, it just says: Quote XXX.XXX.XXX.XXX refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED Just in case, I restarted the docker, and the log says: Quote Done. -> Executing /opt/docker/provision/entrypoint.d/05-permissions.sh -> Executing /opt/docker/provision/entrypoint.d/20-nginx.sh -> Executing /opt/docker/provision/entrypoint.d/20-php-fpm.sh -> Executing /opt/docker/provision/entrypoint.d/20-php.sh -> Executing /opt/docker/bin/service.d/supervisor.d//10-init.sh 2020-10-16 10:58:30,868 INFO Included extra file "/opt/docker/etc/supervisor.d/cron.conf" during parsing 2020-10-16 10:58:30,868 INFO Included extra file "/opt/docker/etc/supervisor.d/dnsmasq.conf" during parsing 2020-10-16 10:58:30,868 INFO Included extra file "/opt/docker/etc/supervisor.d/nginx.conf" during parsing 2020-10-16 10:58:30,868 INFO Included extra file "/opt/docker/etc/supervisor.d/php-fpm.conf" during parsing 2020-10-16 10:58:30,868 INFO Included extra file "/opt/docker/etc/supervisor.d/postfix.conf" during parsing 2020-10-16 10:58:30,868 INFO Included extra file "/opt/docker/etc/supervisor.d/ssh.conf" during parsing 2020-10-16 10:58:30,868 INFO Included extra file "/opt/docker/etc/supervisor.d/syslog.conf" during parsing 2020-10-16 10:58:30,868 INFO Set uid to user 0 succeeded 2020-10-16 10:58:30,876 INFO RPC interface 'supervisor' initialized 2020-10-16 10:58:30,876 INFO supervisord started with pid 1 2020-10-16 10:58:31,878 INFO spawned: 'syslogd' with pid 56 2020-10-16 10:58:31,879 INFO spawned: 'nginxd' with pid 57 2020-10-16 10:58:31,880 INFO spawned: 'php-fpmd' with pid 58 2020-10-16 10:58:31,882 INFO spawned: 'crond' with pid 59 -> Executing /opt/docker/bin/service.d/syslog-ng.d//10-init.sh 2020-10-16 10:58:31,885 INFO success: nginxd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-10-16 10:58:31,885 INFO success: php-fpmd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2020-10-16 10:58:31,885 INFO success: crond entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) -> Executing /opt/docker/bin/service.d/nginx.d//10-init.sh -> Executing /opt/docker/bin/service.d/php-fpm.d//10-init.sh Setting php-fpm user to application -> Executing /opt/docker/bin/service.d/cron.d//10-init.sh [2020-10-16T10:58:31.925772] WARNING: With use-dns(no), dns-cache() will be forced to 'no' too!; [SYSLOG] syslog-ng[56]: syslog-ng starting up; version='3.19.1' [16-Oct-2020 10:58:31] NOTICE: fpm is running, pid 58 [16-Oct-2020 10:58:31] NOTICE: ready to handle connections 2020-10-16 10:58:32,967 INFO success: syslogd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) I haven't changed any settings, but the two \ in the URL. I can't figure it out. Can anyone help? Quote Link to comment
Nanobug Posted October 20, 2020 Share Posted October 20, 2020 (edited) I haven't gotten any further with the XBackBone. So I've put it on standby. Instead I'm trying to get the UniFi-Poller to work, but it doesn't write anything to the database, and I can't find any information on the wiki to help me. I might be missing it though. Can anyone help? EDIT: I need to learn how to spell.... Edited October 20, 2020 by Nanobug Quote Link to comment
Roxedus Posted October 20, 2020 Author Share Posted October 20, 2020 On 10/16/2020 at 11:00 AM, Nanobug said: I haven't changed any settings, but the two \ in the URL. Changed how? the \ needs to be there, because they are escape-characters. the config becomes malformed without it Quote Link to comment
Nanobug Posted October 21, 2020 Share Posted October 21, 2020 7 hours ago, Roxedus said: Changed how? the \ needs to be there, because they are escape-characters. the config becomes malformed without it I've added it again so it says: http:\/\/300.300.300.300:9876 (300 is not my real IP, I just changed it, just in case) When I start it, it says this in the log: Quote -> Executing /opt/docker/bin/service.d/php-fpm.d//10-init.sh Setting php-fpm user to application -> Executing /opt/docker/bin/service.d/nginx.d//10-init.sh [21-Oct-2020 08:12:55] NOTICE: fpm is running, pid 54 [21-Oct-2020 08:12:55] NOTICE: ready to handle connections 2020-10-21 08:12:56,101 INFO success: syslogd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) [php-fpm:access] 127.0.0.1 - 21/Oct/2020:08:13:24 +0200 "GET /index.php" 302 /app/index.php 62.716 4096 79.72% 300.300.300.300 - - [21/Oct/2020:08:13:24 +0200] "GET / HTTP/1.1" 302 5 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36" [php-fpm:access] 127.0.0.1 - 21/Oct/2020:08:13:24 +0200 "GET /index.php" 302 /app/index.php 62.716 4096 79.72% 300.300.300.300 - - [21/Oct/2020:08:13:24 +0200] "GET / HTTP/1.1" 302 5 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.75 Safari/537.36" I get this in the browser (Google Chrome): Quote This site can’t be reached 300.300.300.300 refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED I tried disabling the firewall as well. Any ideas? Quote Link to comment
Roxedus Posted October 21, 2020 Author Share Posted October 21, 2020 1 hour ago, Nanobug said: :9876 Did you change the mapped port, or did you use the default mapped port of 9876? Quote Link to comment
Nanobug Posted October 21, 2020 Share Posted October 21, 2020 7 minutes ago, Roxedus said: Did you change the mapped port, or did you use the default mapped port of 9876? I used the default I think. I only change the port if it's used by something else. Quote Link to comment
MM23 Posted October 21, 2020 Share Posted October 21, 2020 On 9/12/2020 at 4:43 PM, tzahi12345 said: Dev here! You can find the interval over in the settings, it's in the Main tab, called "Check interval". See attached image for reference. Let me know if you have any other questions! Thanks for the helpful response! I love your software by the way, is there anyway you can make it so we can edit an existing subscription, or at least be able to check existing subscription's arguments from the GUI? It would help a lot to know what settings I've set on previous subscriptions. Quote Link to comment
JonathanM Posted October 24, 2020 Share Posted October 24, 2020 On 9/18/2020 at 6:20 PM, tzahi12345 said: Are there really no logs? This is quite strange behavior, if the video shows up in the home screen, the subscriptions *must* exist. Maybe something is preventing them from being shown UI-wise.. do you see any errors in the browser console when you try to look at the subscription? Also, try clicking the dropdown for the subscription's videos and click Go to subscription to see if that works. If the subscriptions exist in the DB, then you don't need to resubscribe. But if they do not, then you will. Sorry you're dealing with this problem, let me know if you get any more details. Could be very helpful if there's a bug hidden in there! Updated the latest nightly, and again, all subs are gone after the update. Which db file in the appdata is supposed to hold sub data? The db.json file has this "subscriptions": [], I've attached the dropdown on one of the videos, no "go to subscription" present. The info gives what looks to me a normal result The subscription page Quote Link to comment
planetwilson Posted October 27, 2020 Share Posted October 27, 2020 On 10/4/2020 at 11:23 PM, lzrdking71 said: Isn't the Duplicacy web gui not free? I’d like to know this too. The docker page suggests so but there’s nothing in the gui for it. I get an error about 2020/10/27 22:30:55 Failed to get the value from the keyring: keyring/dbus: Error connecting to dbus session, not registering SecretService provider: dbus: DBUS_SESSION_BUS_ADDRESS not set does that mean it’s not checking? will it stop working? Quote Link to comment
Fallwater Posted October 29, 2020 Share Posted October 29, 2020 I just started with the Duplicacy unraid container. This key is still default: --hostname=duplicacy-unraid Is this correct, or need i modify this? Quote Link to comment
Banuseka Posted October 30, 2020 Share Posted October 30, 2020 Hi all, suddenly my deemix is not working anymore.... the log says the following: [services.d] Starting with ARL python3: can't open file '/deemix/server.py': [Errno 2] No such file or directory ./run: line 6: cd: /deemix: No such file or directory over and over again. anyone hass an idea how to fix this ?? best, banuseka Quote Link to comment
Roxedus Posted October 30, 2020 Author Share Posted October 30, 2020 2 hours ago, Banuseka said: over and over again. Do you have the latest image? Quote Link to comment
gartner Posted October 30, 2020 Share Posted October 30, 2020 Hi Just installed YoutubeDL-Material. Thanks for the prog. Some videos I can download and some not... it's like fifty fifty. I am missing something to set it up, or should it work out of the box ? I've managed to download some videoes, but also many I did not get to download... here one error log: 2020-10-30T23:04:45.232Z ERROR: Error during parsing:Error: Command failed with exit code 1: /app/node_modules/youtube-dl/bin/youtube-dl -i --dump-json https://youtu.be/*** 2020-10-30T23:04:45.233Z ERROR: failed to parse for urls starting with https://youtu.be/*** 2020-10-30T23:04:48.507Z ERROR: Command failed with exit code 1: /app/node_modules/youtube-dl/bin/youtube-dl -i --dump-json -f best -o video/%(title)s.mp4 --write-info-json --print-json -f best[ext=mp4] https://youtu.be/*** Regards Gartner *** I took away the last bit of the url Quote Link to comment
Banuseka Posted October 31, 2020 Share Posted October 31, 2020 (edited) 9 hours ago, Roxedus said: Do you have the latest image? when i check for updates in the version tab it says „not available“. even a removal and new install did not do the trick... Edited October 31, 2020 by Banuseka info edited Quote Link to comment
Banuseka Posted October 31, 2020 Share Posted October 31, 2020 7 hours ago, Banuseka said: when i check for updates in the version tab it says „not available“. even a removal and new install did not do the trick... OK something is strange... first the server.py is missing, now I had to change "/deem/deemix Music" to "/deem/Music", the server.py is back and deemix is working again. However, I have to do the renaming again after every restart of the container... can someone second this? Quote Link to comment
HellraiserOSU Posted November 2, 2020 Share Posted November 2, 2020 I'm trying to setup jira (god help me) and I'm a little stuck when using NGINX Proxy Manager. I have my url in the Reverse Proxy Entry in the template, and NGNIX Proxy Manager setup to reverse proxy the container. I get into it fine from the outside using the url but any posts or deletes will generate the XSRF check failed response. Thus I can't even get past the initial step of creating a project. Can someone let me know how I should setup NGINX Proxy Manager to handle this? Quote Link to comment
GreenEyedMonster Posted November 3, 2020 Share Posted November 3, 2020 @tzahi12345 I am having issues with youtubedl-material. (Great work by the way.) I just did my first and only install and this is what i get when I try to download a video. 2020-11-03T16:27:57.617Z INFO: YoutubeDL-Material v4.0 started on PORT 17442 2020-11-03T16:28:14.708Z ERROR: Error during parsing:Error: Command failed with exit code 1: /app/node_modules/youtube-dl/bin/youtube-dl --dump-json http://www.youtube.com/watch?v=60ruvzfXQoE 2020-11-03T16:28:14.709Z ERROR: failed to parse for urls starting with https://www.youtube.com/watch?v=60ruvzfXQoE 2020-11-03T16:28:14.809Z ERROR: Command failed with exit code 1: /app/node_modules/youtube-dl/bin/youtube-dl --dump-json -f best -o video/%(title)s.mp4 --write-info-json --print-json -f best[ext=mp4] http://www.youtube.com/watch?v=60ruvzfXQoE Any ideas? Quote Link to comment
pinion Posted November 3, 2020 Share Posted November 3, 2020 (edited) 5 hours ago, GreenEyedMonster said: @tzahi12345 I am having issues with youtubedl-material. (Great work by the way.) I just did my first and only install and this is what i get when I try to download a video. 2020-11-03T16:27:57.617Z INFO: YoutubeDL-Material v4.0 started on PORT 17442 2020-11-03T16:28:14.708Z ERROR: Error during parsing:Error: Command failed with exit code 1: /app/node_modules/youtube-dl/bin/youtube-dl --dump-json http://www.youtube.com/watch?v=60ruvzfXQoE 2020-11-03T16:28:14.709Z ERROR: failed to parse for urls starting with https://www.youtube.com/watch?v=60ruvzfXQoE 2020-11-03T16:28:14.809Z ERROR: Command failed with exit code 1: /app/node_modules/youtube-dl/bin/youtube-dl --dump-json -f best -o video/%(title)s.mp4 --write-info-json --print-json -f best[ext=mp4] http://www.youtube.com/watch?v=60ruvzfXQoE Any ideas? So... a few things going on here because I'm also having issues. I shelled into the running container and it appears they are using NPMs youtube-dl with the last packaged version 3.0.2 from 9 months ago. The issue I was getting when running youtube-dl (2020.05.29 for my version) was some sort of JS error. While in the container I added python and pip and installed youtube-dlc (notice the c on the end) from here: https://github.com/blackjack4494/yt-dlc I was then able to download my video as well as the one you linked to using youtube-dlc instead of youtube-dl. I don't know what the fix is but I'd suggest reworking the docker container so that you could alternatively install youtube-dlc instead of NPMs youtube-dl. Especially with all the hassle youtube-dl is going through with the DMCA right now. --------------------------- Editing this to say... I promise I'm not trying to steal the maintainers thunder here but presenting an alternative that I was able to get working. In Apps look for youtube dl server. Go to install that but change the Repository to towatchlist/twl-dl-server. This person actually kept up on it and has integrated youtube-dlc. From there things appear to be working for me and things will download to the container path you set in Container Path: /youtube-dl Edited November 3, 2020 by pinion Quote Link to comment
GreenEyedMonster Posted November 10, 2020 Share Posted November 10, 2020 On 11/3/2020 at 3:32 PM, pinion said: So... a few things going on here because I'm also having issues. I shelled into the running container and it appears they are using NPMs youtube-dl with the last packaged version 3.0.2 from 9 months ago. The issue I was getting when running youtube-dl (2020.05.29 for my version) was some sort of JS error. While in the container I added python and pip and installed youtube-dlc (notice the c on the end) from here: https://github.com/blackjack4494/yt-dlc I was then able to download my video as well as the one you linked to using youtube-dlc instead of youtube-dl. I don't know what the fix is but I'd suggest reworking the docker container so that you could alternatively install youtube-dlc instead of NPMs youtube-dl. Especially with all the hassle youtube-dl is going through with the DMCA right now. --------------------------- Editing this to say... I promise I'm not trying to steal the maintainers thunder here but presenting an alternative that I was able to get working. In Apps look for youtube dl server. Go to install that but change the Repository to towatchlist/twl-dl-server. This person actually kept up on it and has integrated youtube-dlc. From there things appear to be working for me and things will download to the container path you set in Container Path: /youtube-dl So now it's working after the last update without making changes. Only issue is that it is NOT getting the highest quality. Instead it is going down to super low quality video. Any ideas? Quote Link to comment
pinion Posted November 10, 2020 Share Posted November 10, 2020 17 minutes ago, GreenEyedMonster said: So now it's working after the last update without making changes. Only issue is that it is NOT getting the highest quality. Instead it is going down to super low quality video. Any ideas? I'm using towatchlist/twl-dl-server, are you? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.