Jump to content

Coolsaber57

Members
  • Content Count

    52
  • Joined

  • Last visited

Community Reputation

1 Neutral

About Coolsaber57

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Coolsaber57

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Yeah, not sure how many times I'm going to do that 😂
  2. Coolsaber57

    [Support] Linuxserver.io - Lychee

    Yep, I moved on from Lychee for now. I'm also concerned that it imports all of the pictures into the database, which means the files are no longer on my Share, but my Docker/VM ssd (unassigned drive). I am still looking for a solution that will allow you to keep the photos where they are. I'm trying Photoshow at the moment, but it's quite slow.
  3. Coolsaber57

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Ok I've run into an odd issue, trying to figure out where I am going wrong. I'm trying to proxy the Photoshow docker container with the following config under the https://photos.mydomain.com: # For Photoshow server { listen 443 ssl; listen [::]:443 ssl; server_name photos.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /login; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_photos photoshow; proxy_pass http://$upstream_photos:8083; } } However, when I start up the LE container, I get an error, and the container doesn't start: e': "No such container: 0a7b5297b0bc" Here's my photoshow config for reference: Am I missing something really obvious? Edit: just realized I should have set upstream_photos and used port 80. Resolved my issue.
  4. Coolsaber57

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Hey this is not necessarily what you're looking for, but I had a much easier time passing the Firefox container, then just accessing the Unraid UI inside the firefox container. Much less headache IMO.
  5. Coolsaber57

    [Support] jasonbean - Apache Guacamole

    I'm sorry, I must be blind - is there a link to your repository that I'm missing?
  6. Coolsaber57

    [Support] jasonbean - Apache Guacamole

    Understood, thank you. I may just grab screenshots of my configs and re-create the container at some point considering I don't have a ton of connections.
  7. Coolsaber57

    [Support] jasonbean - Apache Guacamole

    Thanks for the updated template! Quick question: I have a MariaDB container running for NextCloud and Lychee, but currently run this container with the database included. Is there an easy way I can migrate from the current DB-included container to the separate DB-container?
  8. Coolsaber57

    [Support] Linuxserver.io - Lychee

    I'm trying to import a large number of files, but the import process seems to hang after a certain # of pics imported. Sometimes it's ~85, sometimes it's a few hundred, but eventually it stops importing but doesn't tell me. Is there some kind of setting or better way of doing this? I have around 18k pictures in total and importing them a few hundred at a time is painful.
  9. Coolsaber57

    [Support] binhex - Krusader

    This is exactly what I was looking for, thank you so much!
  10. Coolsaber57

    Wake on Lan for Virtual Machines for 6.1+

    Maybe describe your network environment and equipment a bit. Something may be blocking the wol packets also what motherboard and network card. You may need to enable wol in your bios. Hey there, sorry I was just going to investigate my setup if I could get a tip on where to start from the other guy, but my setup includes: Ubiquiti USG Ubiquiti US-48 switch Gigabyte GA-7PESH2 dual socket LGA2011 mainboard w/ 2x e5-2630 v2, connected via 10gbase-T to sfp+ to the US-48 Sending WoL packets via phone app and WebCore (home automation s/w) I'll see how to enable WoL in the bios in my MB, I wasn't aware that was needed. Edit: the default setting for WoL is ON on my MB, and I can double check when I get home, but I would imagine it's enabled.
  11. Coolsaber57

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Hey man, I saw your tip about the lowercase, and I thought I understood what you meant, but then it clicked: the actual name of the docker container has to be changed to lowercase, not just what's in the .conf file. 🤦‍♂️ Anyway, I finally got it to work with the below config, then just updated the settings in the OnlyOffice plugin in NextCloud with the https address: server { listen 443 ssl; server_name docs.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_docs onlyofficedocumentserver; proxy_pass https://$upstream_docs:443; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Forwarded-Proto $scheme; } } Thanks for the help once again.
  12. Coolsaber57

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Hey do you have a source for that? The instructions I see on the docker page show that they create a bridge network if integrating with their Community Server and Mail Server, which, if you are using the LetsEncrypt docker, is already done.
  13. Coolsaber57

    [Support] Linuxserver.io - Letsencrypt (Nginx)

    Hey it's me again, heh. I thought I might try to post here, in case someone has already figured this out. I'm trying to proxy the OnlyOfficeDocumentServer docker container so that I can connect it to NextCloud and edit documents. The issue I'm having is that I am trying to follow the other examples inside the LetsEncrypt container, but there isn't a .sample for the Doc Server (or community server for that matter). This current configuration gives me a 502 error when attempting to access it via the proxy: # only office doc server server { listen 443 ssl; listen [::]:443 ssl; server_name docs.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_docs onlyofficedocumentserver; proxy_pass https://$upstream_docs; } } I get the feeling it'll probably be more complicated than this, but thought I'd check here before embarking on a lot of trial and error. Has anyone done this already?
  14. Coolsaber57

    [support] Siwat's Docker Repository

    Hmm, I still get a 502 bad gateway using https: # only office doc server server { listen 443 ssl; listen [::]:443 ssl; server_name docs.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_docs onlyofficedocumentserver; proxy_pass https://$upstream_docs; } } I'm trying to use the same format as the rest of the proxy confs in the LetsEncrypt folder, but I'm not sure if there's something going wrong there or a better way to do this. If I remove all the "resolver" and set $upstream stuff in favor of a straight proxy_pass https://unraidIP:4432, the LetsEncrypt docker throws a ton of variable errors and fails to start. Do you happen to have this running behind the LetsEncrypt container? Edit: Got it figured out. From a tip in another thread, you have to actually change the name of the Docker container to all lowercase, then the 502 will go away. I then used this config: server { listen 443 ssl; server_name docs.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_docs onlyofficedocumentserver; proxy_pass https://$upstream_docs:443; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $server_name; proxy_set_header X-Forwarded-Proto $scheme; } } After this, I just went back into the OnlyOffice plugin settings, then entered the https address into the settings and voila! I can open docs in NextCloud now!