njdowdy

Members
  • Content Count

    31
  • Joined

  • Last visited

Everything posted by njdowdy

  1. I am experiencing an issue with calibre-web when reverse proxied through nginx via this container. These are the nginx configs I have set for this subdomain: Scheme: http HTTP/2 Support: On The calibre-web container is accessible via the internet and works fine for a short time. I do get a message that "You are not securely connected to this site" and that "parts of this page are insecure (such as images)" (mixed content). After some amount of activity (or 2.5-5 minutes of inactivity), I get re-directed to the login page. This re-direct tends to trigger more often if I am cl
  2. SOLVED: Turned out to be address via a later firmware update to the router. Hello! Thanks in advance for checking out my question. TLDR; I installed a new router and now my plugins and community applications pages are very slow to load and pulling new docker containers does not work / takes a very long time. I tried many steps to resolve, but the issue persists. Before yesterday I was running my unraid server (version 6.9.0-rc2) on my home network. I purchased a new router (QNAP QHora-301W w/ up-to-date firmware) and plugged my unraid server into a 10Gbit LAN port. Nothing el
  3. Actually, I was going to figure out how to set up a VPN container, but then I discovered how to pass the youtube API key and cookies.txt from within the youtube-dl container. Once I did that, the problems stopped. At least, for now! I also saw there are some options in there to include a sleep interval between downloads to keep the requests/time lower. Thanks!
  4. That worked! It looks so much better now. Thank you!
  5. Did the "too many requests" issue resolve for you? I'm in the same boat. Can I ask how you added the cookie and youtube API to the docker? NOTE: I have a cookies.txt from the firefox extension and an API key. Just wondering how to input into the template. Thanks!
  6. The ferdi resolution is set to 1920x1080 for these images. I did take a screenshot of only a small region of that, just to demonstrate the artifacts. That was blown up to a high resolution only to make the artifacts clearly visible. They are noticeable at the resolution of 1920x1080 in the browser window. I don't think I'm stretching the image with novnc. Scaling mode: none. I have made no other adjustments elsewhere. Only setting the resolution in the template. Here are my novnc settings: To me, your posted image actually has these noticeable artifacts at the posted resolution
  7. Thank you for your reply! While I was trying to obtain the information you requested, this functionality starting working! It now adjusts the resolution at least to 1600x900 and 1920x1080. So, that's great! I have no idea what changed... However, I am experiencing what I assume are compression artifacts. Is there anything I can do about this? See: I have experienced this in other dockers using novnc, but those dockers included an option in the side-bar menu > "Settings" > "Advanced" to adjust compression level. That seems to be missing here (other docker on left; ferdi do
  8. I can't get the ferdi-client docker to display at any resolution higher than 1280x768 (the default setting). Whenever I change it in the docker template, the container starts fine (no errors in the logs) and I can even establish a connection via noVNC. However, I just get a black screen with the dimensions of the desired resolution. Is it possible to increase the resolution? This docker is not usable at the default resolution for me Thanks!
  9. !SOLVED: see below if you have this problem Sorry to be such a noob, but I'm also have trouble with finding the default user and password. I'm aware the documentation states that these are logged to STDOUT, however I cannot seem to find any credentials in the logs. I checked the container logs with: docker logs Mango > /boot/MangoLog.txt Which yields only: _| _| _|_| _|_| _|_|_| _|_|_| _|_|_| _|_| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _| _|
  10. I believe the issue was with my new ISP. I'm using CloudFlare now without issue. Thanks for taking the time to respond.
  11. I'm trying to do the same (also to serve a development version of a flask application). I looked at @waster's recommendation, however the options mentioned in the documentation don't appear for me. It says at the top of the page that this is a "Professional" feature. This PyCharm seems to be the community edition. Is this possible with this docker? Thanks in advance!
  12. I'm trying to replace pgadmin4. The github page for this project mentions this can: - Data export/migration in multiple formats (does this functionality similar to pg_backup & pg_restore?) - Generate entity diagrams I'm not able to do these out of the box. I can export tables one at a time, but not as a dump. And I don't see a "diagram" tab on entities which should support a diagram representation. Running :latest. There's no info on the docker page about additional configuration steps. Am I missing something or are these things not supported? Thanks for the info!
  13. I "resolved" the issue described in my previous post. For those facing similar errors renewing certificates, check your ISP policies. My new ISP has a stricter port policy than my previous one. This ISP blocks port 80, which breaks the Let'sEncrypt certificate renewal process. My solution was to integrate CloudFlare with NPM. That allows for a work around to the ISP blocking port 80. I hope that helps others.
  14. I recently moved and am now having problems renewing my certificates. My issues are similar to what others have posted here, but I am having a difficult time finding whether a solution was found. The problem is: 1. When the docker is first started the log says: ⚠ warning Command failed: /usr/bin/certbot certonly --non-interactive --config "/etc/letsencrypt.ini" --cert-name "npm-31" --agree-tos --email "myEmail@email.com" --preferred-challenges "dns,http" --domains "<mysubdomain.mydomain.com" Another instance of Certbot is already running And then a bunch of challenges fail.
  15. Is there any trick to getting this to work with nginx proxy manager? EDIT: Nevermind. Solved. Nginx scheme needs to be http not https. Not sure why though. But nextcloud does that to me too. If I visit https://subdomain.mydomain.com it seems fine. I had to use the docker link fix with MONGO_URL earlier in the thread, which worked great (so mongo and wekan on same docker network as nginxproxymanager). I changed the ROOT_URL to https://subdomain.mydomain.com In nginx config I've got https://<unraid_ip>:5555 linked to subdomain.mydomain.com But I keep getting 502 bad ga
  16. Can someone please advise me on how to pass my postgres docker to the Taskcafe docker template? I have a postgres11 docker named "postgres-taskcafe" running on <my_unraid_ip>:5433 In the Taskcafe template I have tried passing the following into TASKCAFE_DATABASE_HOST: postgres-taskcafe; <my_unraid_ip>:5433 With the following error: error="dial tcp: lookup postgres-taskcafe on 1.1.1.1:53: no such host" Network Type set to "Bridge" like the rest of my dockers. I'm sure I'm making a noob mistake. Thanks in advance!
  17. I have a reverse-proxy for myself, but I need to also SSH into my university to upload and execute code developed in vscode remotely on a cluster.
  18. Do we need a docker mod to get remote development tools? I did not see anything like that in the list of currently available docker mods. See snapshot of my local install of VS that lists some of these. These don't show up as search results using the extensions search from within this docker. Can anyone share info on how to set up ssh for remote development from within this docker? Thanks!!
  19. @phreeq, me too! It's amazing so far though, despite the learning curve. Very happy it's in an unraid docker thanks @fithwum Happy gaming everyone
  20. @phreeq, thanks so much for the nginx config. It's working great. I was wondering though what you meant by "# Make sure that your dns has a cname set for dokuwiki". Can you elaborate on that the dokuwiki thing or was that a leftover comment from a different template you copied as a base for this template? Also, can anyone confirm if the default behavior for token images is to point to "icons/svg/mystery-man.svg"? I see most of the token images point to this placeholder and I wasn't sure if this was proper default behavior or if I've misconfigured something. When I change the path to
  21. This wasn't the issue as far as I can tell. I run this docker on port 6081, your krusader docker on 6082, and the Filebot was on 7813 and 7913. Your dockers don't conflict with each other's VNC - I can run both simultaneously. Not sure why Filebot broke, but for now I'm just using the Windows installed version and accessing files for renaming via shares. Maybe I'll figure it out someday
  22. Thanks for the help. It was a transcode mapping problem! Cheers!
  23. I got this docker up and running, but it seems it has broken my FileBot and Krusader (djaydev) dockers. I can't access them after installing this docker. I think it has something to do with vnc, because the dockers come up, but I get the following error displayed: "server disconnected (code: 1006)". Additionally, the log file of Krusader was displaying "Not connected to D-Bus server". I removed the djaydev Krusader and replaced with binhex's Krusader docker - that one works fine. There's no alternative to the FileBot image in community applications though. I removed it and re-installed i
  24. I'm experience a strange problem. Whenever I try to play .m4a files through the browser (chrome & firefox), transcode fails and playback does not start. Logs say: "DEBG 'plexmediaserver' stderr output: Jobs: failed with chdir, errno=2" However, if I use the plex android app, the files play fine. FLAC/mp3/etc formats work fine in browser and in app. What could be going wrong?
  25. @aptalca, after digging around further, I stumbled on some resources for setting up the stream module (e.g., https://www.nginx.com/blog/tcp-load-balancing-udp-load-balancing-nginx-tips-tricks/. However, I still haven't been able to get it up and running, mainly because I'm not sure what the proxy-conf file should look like for a docker needing to utilize the stream module. I added the following to my nginx.conf (previous was default nginx.conf that comes with the letsencrypt docker): http{ #default stuff } stream { upstream stream_backend { # 10.20.30.222:5432 is the postgres