Jump to content

plantsandbinary

Members
  • Posts

    346
  • Joined

  • Last visited

Everything posted by plantsandbinary

  1. I run 2 domains from the same letsencrypt docker container. A Heimdall start page and a Ghost blog. They are on different server blocks and I own both domains via same provider = Namecheap. Both of them resolve to the same I.P. address, but for some reason only one of them is now working after restarting my machine. My first site (Heimdall) loads fine, no problem at all. It was up again in mere minutes after restarting. The second site (Ghost blog) does not load at all. It simply ends up timing out with "The page took too long to respond" error. However, I can go to the site locally on my network at eg. 192.168.1.10:1234 What could have happened? Why is one of the server blocks working but the other is timing out and won't load? I have pinged both domain urls, both of them resolve to the same I.P. (edit: oops no they don't, my bad) however the one that loads resolves with 1ms response time, the one that does not load resolves with about 23ms response time. I also tried tracing them, here is the first one: 1 <1 ms <1 ms <1 ms *********-58c1e5-231.******.**.** [88.***.***.231] Now here is the one that does not work: 1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1] 2 * * * Request timed out. 3 28 ms 24 ms 29 ms *********-58c02e-173.******.**.** [88.***.***.173] Can anyone tell me what is going on? I´ve stopped the docker service, invoked the mover. Updated all my containers etc. there are no errors in my log. What's going on?
  2. I still can't get this to work. I can connect to the Unraid server's OpenVPN server. But none of the services on my home network are available. 192.168.1.1 (router) or 192.168.1.50 (unraid server) aren't available, neither is anything else. Also after only about 2 minutes it disconnects me and says "Invalid credentials". Even though my credentials are fine and they work to login in the first place. Tue Sep 04 15:05:05 2018 OpenVPN 2.4.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 26 2018 Tue Sep 04 15:05:05 2018 Windows version 6.2 (Windows 8 or greater) 64bit Tue Sep 04 15:05:05 2018 library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10 Enter Management Password: Tue Sep 04 15:05:05 2018 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:25340 Tue Sep 04 15:05:05 2018 Need hold release from management interface, waiting... Tue Sep 04 15:05:06 2018 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:25340 Tue Sep 04 15:05:06 2018 MANAGEMENT: CMD 'state on' Tue Sep 04 15:05:06 2018 MANAGEMENT: CMD 'log all on' Tue Sep 04 15:05:06 2018 MANAGEMENT: CMD 'echo all on' Tue Sep 04 15:05:06 2018 MANAGEMENT: CMD 'bytecount 5' Tue Sep 04 15:05:06 2018 MANAGEMENT: CMD 'hold off' Tue Sep 04 15:05:06 2018 MANAGEMENT: CMD 'hold release' Tue Sep 04 15:05:07 2018 MANAGEMENT: CMD 'username "Auth" "markus"' Tue Sep 04 15:05:07 2018 MANAGEMENT: CMD 'password [...]' Tue Sep 04 15:05:07 2018 WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead. Tue Sep 04 15:05:07 2018 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Tue Sep 04 15:05:07 2018 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Tue Sep 04 15:05:07 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]<PUBLIC.IP.REMOVED> Tue Sep 04 15:05:07 2018 Socket Buffers: R=[65536->100000] S=[65536->100000] Tue Sep 04 15:05:07 2018 UDP link local: (not bound) Tue Sep 04 15:05:07 2018 UDP link remote: [AF_INET]<PUBLIC.IP.REMOVED> Tue Sep 04 15:05:07 2018 MANAGEMENT: >STATE:1536062707,WAIT,,,,,, Tue Sep 04 15:05:07 2018 MANAGEMENT: >STATE:1536062707,AUTH,,,,,, Tue Sep 04 15:05:07 2018 TLS: Initial packet from [AF_INET]<PUBLIC.IP.REMOVED>:1194, sid=a5a3543b 823aedd8 Tue Sep 04 15:05:07 2018 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this Tue Sep 04 15:05:07 2018 VERIFY OK: depth=1, CN=OpenVPN CA Tue Sep 04 15:05:07 2018 VERIFY OK: nsCertType=SERVER Tue Sep 04 15:05:07 2018 VERIFY OK: depth=0, CN=OpenVPN Server Tue Sep 04 15:05:07 2018 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA Tue Sep 04 15:05:07 2018 [OpenVPN Server] Peer Connection Initiated with [AF_INET]<PUBLIC.IP.REMOVED>:1194 Tue Sep 04 15:05:08 2018 MANAGEMENT: >STATE:1536062708,GET_CONFIG,,,,,, Tue Sep 04 15:05:08 2018 SENT CONTROL [OpenVPN Server]: 'PUSH_REQUEST' (status=1) Tue Sep 04 15:05:08 2018 PUSH: Received control message: 'PUSH_REPLY,explicit-exit-notify,topology subnet,route-delay 5 30,dhcp-pre-release,dhcp-renew,dhcp-release,route-metric 101,ping 12,ping-restart 50,auth-tokenSESS_ID,comp-lzo yes,redirect-gateway def1,redirect-gateway bypass-dhcp,redirect-gateway autolocal,route-gateway 172.27.224.1,dhcp-option DNS 9.9.9.9,register-dns,block-ipv6,ifconfig 172.27.224.10 255.255.240.0,peer-id 0,cipher AES-256-GCM' Tue Sep 04 15:05:08 2018 Obsolete option --dhcp-release detected. This is now on by default Tue Sep 04 15:05:08 2018 Unrecognized option or missing or extra parameter(s) in [PUSH-OPTIONS]:18: block-ipv6 (2.4.6) Tue Sep 04 15:05:08 2018 OPTIONS IMPORT: timers and/or timeouts modified Tue Sep 04 15:05:08 2018 OPTIONS IMPORT: explicit notify parm(s) modified Tue Sep 04 15:05:08 2018 OPTIONS IMPORT: compression parms modified Tue Sep 04 15:05:08 2018 OPTIONS IMPORT: --ifconfig/up options modified Tue Sep 04 15:05:08 2018 OPTIONS IMPORT: route options modified Tue Sep 04 15:05:08 2018 OPTIONS IMPORT: route-related options modified Tue Sep 04 15:05:08 2018 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified Tue Sep 04 15:05:08 2018 OPTIONS IMPORT: peer-id set Tue Sep 04 15:05:08 2018 OPTIONS IMPORT: adjusting link_mtu to 1625 Tue Sep 04 15:05:08 2018 OPTIONS IMPORT: data channel crypto options modified Tue Sep 04 15:05:08 2018 Data Channel: using negotiated cipher 'AES-256-GCM' Tue Sep 04 15:05:08 2018 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Tue Sep 04 15:05:08 2018 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key Tue Sep 04 15:05:08 2018 interactive service msg_channel=792 Tue Sep 04 15:05:08 2018 ROUTE_GATEWAY 192.168.43.1/255.255.255.0 I=10 HWADDR=9c:b6:d0:f6:b9:93 Tue Sep 04 15:05:08 2018 open_tun Tue Sep 04 15:05:08 2018 TAP-WIN32 device [Ethernet 3] opened: \\.\Global\{BBFBF683-27C3-421B-BF23-29783C56E882}.tap Tue Sep 04 15:05:08 2018 TAP-Windows Driver Version 9.21 Tue Sep 04 15:05:08 2018 Set TAP-Windows TUN subnet mode network/local/netmask = 172.27.224.0/172.27.224.10/255.255.240.0 [SUCCEEDED] Tue Sep 04 15:05:08 2018 Notified TAP-Windows driver to set a DHCP IP/netmask of 172.27.224.10/255.255.240.0 on interface {BBFBF683-27C3-421B-BF23-29783C56E882} [DHCP-serv: 172.27.239.254, lease-time: 31536000] Tue Sep 04 15:05:08 2018 Successful ARP Flush on interface [50] {BBFBF683-27C3-421B-BF23-29783C56E882} Tue Sep 04 15:05:08 2018 NOTE: Release of DHCP-assigned IP address lease on TAP-Windows adapter failed: An address has not yet been associated with the network endpoint. (code=1228) Tue Sep 04 15:05:12 2018 TAP: DHCP address renewal succeeded Tue Sep 04 15:05:12 2018 do_ifconfig, tt->did_ifconfig_ipv6_setup=0 Tue Sep 04 15:05:12 2018 MANAGEMENT: >STATE:1536062712,ASSIGN_IP,,172.27.224.10,,,, Tue Sep 04 15:05:17 2018 TEST ROUTES: 1/1 succeeded len=0 ret=1 a=0 u/d=up Tue Sep 04 15:05:17 2018 ROUTE remote_host is NOT LOCAL Tue Sep 04 15:05:17 2018 C:\WINDOWS\system32\route.exe ADD <PUBLIC.IP.REMOVED> MASK 255.255.255.255 192.168.43.1 Tue Sep 04 15:05:17 2018 Route addition via service succeeded Tue Sep 04 15:05:17 2018 C:\WINDOWS\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 172.27.224.1 Tue Sep 04 15:05:17 2018 Route addition via service succeeded Tue Sep 04 15:05:17 2018 C:\WINDOWS\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 172.27.224.1 Tue Sep 04 15:05:17 2018 Route addition via service succeeded Tue Sep 04 15:05:17 2018 Initialization Sequence Completed Tue Sep 04 15:05:17 2018 Register_dns request sent to the service Tue Sep 04 15:05:17 2018 MANAGEMENT: >STATE:1536062717,CONNECTED,SUCCESS,172.27.224.10,<PUBLIC.IP.REMOVED>,1194,, Tue Sep 04 15:07:39 2018 [OpenVPN Server] Inactivity timeout (--ping-restart), restarting Tue Sep 04 15:07:39 2018 C:\WINDOWS\system32\route.exe DELETE <PUBLIC.IP.REMOVED> MASK 255.255.255.255 192.168.43.1 Tue Sep 04 15:07:39 2018 Route deletion via service succeeded Tue Sep 04 15:07:39 2018 C:\WINDOWS\system32\route.exe DELETE 0.0.0.0 MASK 128.0.0.0 172.27.224.1 Tue Sep 04 15:07:39 2018 Route deletion via service succeeded Tue Sep 04 15:07:39 2018 C:\WINDOWS\system32\route.exe DELETE 128.0.0.0 MASK 128.0.0.0 172.27.224.1 Tue Sep 04 15:07:39 2018 Route deletion via service succeeded Tue Sep 04 15:07:39 2018 Closing TUN/TAP interface Tue Sep 04 15:07:39 2018 TAP: DHCP address released Tue Sep 04 15:07:39 2018 SIGUSR1[soft,ping-restart] received, process restarting Tue Sep 04 15:07:39 2018 MANAGEMENT: >STATE:1536062859,RECONNECTING,ping-restart,,,,, Tue Sep 04 15:07:39 2018 Restart pause, 5 second(s) Tue Sep 04 15:07:44 2018 WARNING: --ns-cert-type is DEPRECATED. Use --remote-cert-tls instead. Tue Sep 04 15:07:44 2018 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Tue Sep 04 15:07:44 2018 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Tue Sep 04 15:07:44 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]<PUBLIC.IP.REMOVED>:1194 Tue Sep 04 15:07:44 2018 Socket Buffers: R=[65536->100000] S=[65536->100000] Tue Sep 04 15:07:44 2018 UDP link local: (not bound) Tue Sep 04 15:07:44 2018 UDP link remote: [AF_INET]<PUBLIC.IP.REMOVED>:1194 Tue Sep 04 15:07:44 2018 MANAGEMENT: >STATE:1536062864,WAIT,,,,,, Tue Sep 04 15:07:44 2018 MANAGEMENT: >STATE:1536062864,AUTH,,,,,, Tue Sep 04 15:07:44 2018 TLS: Initial packet from [AF_INET]<PUBLIC.IP.REMOVED>:1194, sid=408c80a1 59f121a6 Tue Sep 04 15:07:44 2018 VERIFY OK: depth=1, CN=OpenVPN CA Tue Sep 04 15:07:44 2018 VERIFY OK: nsCertType=SERVER Tue Sep 04 15:07:44 2018 VERIFY OK: depth=0, CN=OpenVPN Server Tue Sep 04 15:07:44 2018 WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1550', remote='link-mtu 1558' Tue Sep 04 15:07:44 2018 WARNING: 'cipher' is used inconsistently, local='cipher AES-256-GCM', remote='cipher AES-256-CBC' Tue Sep 04 15:07:44 2018 WARNING: 'auth' is used inconsistently, local='auth [null-digest]', remote='auth SHA1' Tue Sep 04 15:07:44 2018 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA Tue Sep 04 15:07:44 2018 [OpenVPN Server] Peer Connection Initiated with [AF_INET]<PUBLIC.IP.REMOVED>:1194 Tue Sep 04 15:07:46 2018 MANAGEMENT: >STATE:1536062866,GET_CONFIG,,,,,, Tue Sep 04 15:07:46 2018 SENT CONTROL [OpenVPN Server]: 'PUSH_REQUEST' (status=1) Tue Sep 04 15:07:46 2018 AUTH: Received control message: AUTH_FAILED Tue Sep 04 15:07:46 2018 SIGUSR1[soft,auth-failure] received, process restarting Tue Sep 04 15:07:46 2018 MANAGEMENT: >STATE:1536062866,RECONNECTING,auth-failure,,,,, Tue Sep 04 15:07:46 2018 Restart pause, 5 second(s) Also it seems to be assigning me some kind of local I.P. like 172.27.244.** when really I think I am meant to be 192.168.1.** or something. What am I doing wong?
  3. The old theme was pretty bad but the only thing I don't like really is that for UX designers like myself. White text on a black background is kind of seen as heresy in UX development. You're supposed to at least have a solution that is black text and white or somewhat kind of light background. So the fact that we only have a black option is kind of weird. I'm still getting used to it but it's still a better design than before.
  4. 16GB of ECC DDR4 RAM because I thought I'd be using loads of VMs and other stuffs but now all I really use is just docker and I don't need basically any RAM at all for that. So it's just sitting there lol.
  5. NordVPN Now can someone tell me why I can't download anything via RSS?
  6. Hey folks. I can't get RSS to auto download anything. Whenever it tries I just get an error: [03.09.2018 21:44:43] Error loading torrent. (<torrentURL>)
  7. I was going about this the wrong way. I got it sorted about 5 days ago, don't really remember how but I got a lot of help from redditors, and I am running my blog on a different domain which is exactly what I wanted and it works fine. I'm going to delete my mailgun account because I don't need it. Setting it up with MariaDB worked far better than MySQL.
  8. Was the update important? Sounds like a pain so I don't think I will update at this time.
  9. Sorry this is a little long. **TL;DR at the bottom!** I'm trying to use the official Ghost docker container on Unraid. As the CA version we have is not working with MySQL. That's another story. First I find and install the container from the 'Docker hub': Then I install it, and set the network interface to the custom interface I made [web] where I run almost all of my containers with reverse proxy: Installation is successful but the container isn't being served at the same I.P. address like the rest of my containers (it should be 192.168.1.50): The log shows that the installation was fine and database tables were made and the blog should now be accessible but it isn't: What extra steps do I need to do here? I'm trying to get this served under the Letsencrypt container that I already have installed. Basically I have a domain (eg. server1.com) where I have a landing page with access to all my reverse proxy'd containers. But I want to host this Ghost blog on a different domain (eg. ghostblog.com). The problem is that without it being served at the same I.P. as the rest of my containers, nothing can connect to it. I can't access the Ghost landing page at all. It does work however if I set the network type to Bridge and then type out a custom I.P. eg. 192.168.1.80 The problem then is that when I try and reverse proxy the container with a config like this in my server block: server { listen 443 ssl; server_name ghostblog.com; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_redirect off; proxy_set_header Host $http_host; proxy_pass http://192.168.1.80:2368; } } I just get a generic "Bad Gateway" error. I'd use the Community Applications docker image but it doesn't work any more because the mysql container it relies on hasn't been updated in ages. Also it requires a separate relational database, and it requires mailgun which I don't want to use. I should be able to use the official image without any problems. How are other people doing this? I'd rather not set up VMs etc. and do it that way if possible. _______________________________ TL;DR: I'm trying to set up the official Ghost docker container (not the CA one) to run Ghost on my Unraid server. But it won't give me an I.P. address unless I set the network to "Bridged" and assign it a custom I.P. but if I do that, I can't reverse proxy the container without getting a 502 Gateway Error. What's the solution here?
  10. Ghost docker isn't working any more. Seems to be a problem with the MySQL docker needing to be updated. Here's the log: [2018-08-26 16:11:29] [31mERROR[39m [31m [31mNAME: DatabaseError[39m [31mCODE: ER_NOT_SUPPORTED_AUTH_MODE[39m [31mMESSAGE: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client[39m [37mlevel:[39m[37mnormal[39m [33mUnknown database error[39m [37mDatabaseError: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client at DatabaseError.KnexMigrateError (/var/lib/ghost/versions/2.0.3/node_modules/knex-migrator/lib/errors.js:7:26) at new DatabaseError (/var/lib/ghost/versions/2.0.3/node_modules/knex-migrator/lib/errors.js:56:26) at connection.raw.catch (/var/lib/ghost/versions/2.0.3/node_modules/knex-migrator/lib/database.js:40:19) at tryCatcher (/var/lib/ghost/versions/2.0.3/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/var/lib/ghost/versions/2.0.3/node_modules/bluebird/js/release/promise.js:512:31) at Promise._settlePromise (/var/lib/ghost/versions/2.0.3/node_modules/bluebird/js/release/promise.js:569:18) at Promise._settlePromise0 (/var/lib/ghost/versions/2.0.3/node_modules/bluebird/js/release/promise.js:614:10) at Promise._settlePromises (/var/lib/ghost/versions/2.0.3/node_modules/bluebird/js/release/promise.js:689:18) at Async._drainQueue (/var/lib/ghost/versions/2.0.3/node_modules/bluebird/js/release/async.js:133:16) at Async._drainQueues (/var/lib/ghost/versions/2.0.3/node_modules/bluebird/js/release/async.js:143:10) at Immediate.Async.drainQueues (/var/lib/ghost/versions/2.0.3/node_modules/bluebird/js/release/async.js:17:14) at runCallback (timers.js:810:20) at tryOnImmediate (timers.js:768:5) at processImmediate [as _immediateCallback] (timers.js:745:5) Error: ER_NOT_SUPPORTED_AUTH_MODE: Client does not support authentication protocol requested by server; consider upgrading MySQL client Could you please set this up to work with MariaDB, or even better. Could you set it up to work without even needing a relational database? It's definitely possible as shown here: https://blog.alexellis.io/your-ghost-blog/ Relational databases are a total pain in the ass to setup and maintain and they're really easily corrupted. Finally, is mailgun also really necessary? They want my credit card information AND my mobile phone number. AFAIK the SMTP part of Ghost is just for getting email notifications of new comments and for also making posts via email etc. but I think most of us don't need or care about that. Especially when Ghost for desktop has notifications built in and there are also Ghost plugins for Desktop notifications via eg. Chrome etc. Could you please look into these issues and look at making the install process more streamlined?
  11. No I asked specifically HERE in this thread about reverse proxying this particular container with letsencrypt. I don't have memory problems, someone deleted my post. It's still indexed in various search engines but the link just redirects to the first page in this thread. I shouldn't have to spell this out. There is literally no reason why my post should have been deleted. If someone has a working reverse proxy config for this, please share it.
  12. Anyone got a working reverse proxy .conf for this? Could you please share.
  13. It doesn't work. I've literally tried everything. I can see all information except for docker containers, vms, or any of my logs what-so-ever from the Android app. I'm using the latest plugin version and the latest Android store app. It just says that I need to install the server. Can you please give me the login information so I can see maybe if there's a setting in there I need to change or something, I dunno.
  14. I know I asked somewhere how to reverse proxy this with the letsencrypt container. Was my post deleted? I cannot find it any more. It shows up in Google that I asked, but my post is literally nowhere in this thread. I'd still like to know how to reverse proxy this docker app. If anyone has a proxy .conf file or something I'd honestly appreciate it and if my post was deleted I would like to know why because it's a legitimate question.
  15. For people having issues getting this to work under reverse proxy with linuxserver.io's letsencrypt docker, see my post in the other thread here for the vpn version of qBittorrent: Would be great to see an official vpn version of this container set up by linuxserver.io
  16. After 3 days and about 20 cups of coffee trying to work how to reverse proxy this container I finally got it sorted. Using linuxserver.io's letsencrypt docker. I made my own proxy.conf file here: # qBittorrent devs on Github indicated the Origin and Referer headers needed to be surpressed, # and that the X-Forwarded-Host needed to match what was seen in the browser, # as of version 4.0.3 these are the working settings. # Note: For some users, several windows in the Web UI will still be blank, such as when adding # a new torrent from a URL/magnet or local file. # If so, uncomment the last line "add_header" # to enable password access, uncomment the two auth_basic lines location /qbt/ { # auth_basic "Restricted"; # auth_basic_user_file /config/nginx/.htpasswd; proxy_pass http://192.168.1.50:8080/; proxy_set_header X-Forwarded-Host $server_name:$server_port; proxy_hide_header Referer; proxy_hide_header Origin; proxy_set_header Referer ''; proxy_set_header Origin ''; # add_header X-Frame-Options "SAMEORIGIN"; } This successfully fixes the redirection issue due to mismatching header data and well... it just works in general. I tried for ages to get it working on a subdomain but I just couldn't. Always ended up getting the blank page issue. Either way I'm not picky. This works fine for my needs. Credits mostly to: https://github.com/qbittorrent/qBittorrent/wiki/NGINX-Reverse-Proxy-for-Web-UI The developer of this container @ MarkusMcNugen may be able to use the same thing to fix the inherent issue regarding the webUI redirect problem mentioned in the first post.
  17. I've got a problem with this. Using UNRAID 6.5.3 I can't see any of my docker containers, vms, or any of my logs what-so-ever from the Android app. All I can do is see storage space and spin down/shutdown the server. Also what's the login information for the Webui via the plugins tab? I do have that installed.
  18. @MarkusMcNugen Hi and firstly thanks so much for this amazing docker. The VPN credentials part was by far the easiest of any docker I've used here. Binhex's dockers are great but require a crazy amount of configuring to get working. Just being able to drop my .ovpn config server file of choice in and throw in my username and password is exactly the kind of simplicity I honestly expected from other dockers, instead of being tailored the hard way to only work with one or two providers. I have a problem though. No matter what I do or what interface or port I choose, I absolutely cannot open the WebUI. You said that clicking "WebUI" from unraid doesn't work. But neither does going to http://<MYIP>:8080 or whatever port that I pick. I've tried every interface I've created and made available except Host. I either just get a completely blank page or a "page cannot be displayed" error. Can you give me a hand? Also is there any chance you could set up some kind of SSL and .htaccess security for this? I know I'm just being lazy asking for it but running over HTTP is kinda crazy in this day and age. When I get the WebUI sorted I'm going to try and reverse proxy this so I can access it from the web but keep it secure with .htaccess. I'm happy to do both in the meantime but without the webui loading I can't do anything. I'd post a log but it looks like everything is meant to be working correctly. It's just the UI that does not load. I did attach my .ovpn config file though. Here's the last part: Thanks, and I seriously hope I see more dockers from you with the same simplicity. se44.nordvpn.com.udp.ovpn
  19. The watch folder apparently works for everyone else, so it may be an unraid specific problem. Could you please look at it? As for port fowarding I read the readme.md and got it sorted.
  20. Can I get some help getting this to work with NordVPN? Has anyone else got it going? I'd search the thread but there doesn't seem to be the option on the forums here and there's 135 pages...
  21. Hi. Thanks for the Transmission_VPN docker. It's great. I'm using it with NordVPN. Took some trouble but it worked eventually. I've got some issues though I'd like help with. 1. The watch folder doesn't work. I set it to: /mnt/user/tank/user/downloads/[[[[torrentfiles]]]/ I've tried many other names too: eg. /- Torrents or just /torrentfiles etc. Nothing works. It doesn't upload the .torrent files from that directory and then delete them after being added. 2. The update/refresh speed of the UI seems really slow whilst watching a download. It's about 3s or something. Is there a way to change it so it refreshes every 1s or even faster actually? 3. What do we do about port forwarding? What takes precedence here? The VPN port on the docker config page is 1198, but the port listed in the Transmission config on the web-ui is: 51413. Then there's the VPN port that my provider says I should use for torrenting. If I even change the port in the web ui to something else, does that persist on reload or not? So which port is really the proper port for downloading that I need to forward?
  22. Any idea how to run this container through https instead of through http? Default setting is sadly http with no cert autogen or anything.
  23. I realised I should probably upgrade my Unraid installation. I'm running 6.4.1. I'll upgrade it to 6.5.3 and hopefully it'll just work out of the box using default proxy confs in letsencrypt.
  24. Yeah a different PC did the job for me. Had this issue with both a locally downloaded .zip and downloading via the USB creator. A different PC and USB port helped.
  25. Hey @CHBMB I'm having the same problem as this guy and trying to do the exact same thing with Heimdall but through letsencrypt as a reverse proxy but I'm a little behind maybe. I have a domain hat I own eg. "mysite.com" and I've set it up to work over duckdns to connect to letsencrypt's docker front page. So that's done. Now I want to setup Heimdall to work over reverse proxy, with security and I'm trying to follow these instructions on the github page: https://github.com/linuxserver/Heimdall#reverse-proxy I haven't been able to get this working. I'm trying to edit the file site-confs/default file in my letsencrypt docker. I'm not sure if this is the right one though as it seems to be in a different path than the one you both have. I don't have: /config/letsencrypt/nginx/site-confs/ ---- inside the letsencrypt docker. Mine is: /config/nginx/site-confs/ So /config/nginx/site-confs/default seems to be my config file. I've got the Heimdall docker setup over port 443. Letsencrypt docker running on port 81 for http and 444 for https. I'm pretty sure portforwarding is set up correctly. So I added the line inside the letsencrypt docker: /config/nginx/site-confs/default # Heimdall location /heimdall { include /config/nginx/proxy.conf; proxy_pass https://192.168.1.206:443/; } After restarting the docker I navigated to: https://mysite.com/heimdall Input the username and password at the .htaccess prompt (this .htaccess comes from the Heimdall docker not the letsencrypt docker) and none of the images or links on the Heimdall page work... https://www.***mysite***.com/heimdall My page looks like this, none of the images are loading. What's left to do?
×
×
  • Create New...