bigbangus

Members
  • Content Count

    85
  • Joined

  • Last visited

Community Reputation

14 Good

About bigbangus

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Trying to overachieve here and get Guac working with a separate MariaDB. I followed the spacer invader mariadb nextcloud instructions to make a guacamole user and db with all the privileges. Then I copied and pasted the schema instructions into mariadb console with the db selected and it seemed like it worked. Then I did the same to create the guacadmin user. But when I go to WebGUI of Guac I get an error. I've got guacamole.properties set as: guacd-hostname: localhost guacd-port: 4822 mysql-hostname: x.x.x.x (unraid server) mysql-port: 3306
  2. Are you keeping the HA container on the host network, or have you moved it to an isolated 'proxynet'?
  3. Is it safe to have nginx point to something on the host network? In addition to this proxy-conf modification, what do you need to define in the configuration.yaml of the appdata of the HA container?
  4. What line did you add to the config file. I'm having some issues finding what it needs to be. Same issue. Thanks.
  5. Yup that fixed the local WebUI access issue! "A24" in https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md In binhex-delugevpn container: Add 'Variable' with 'KEY' as 'ADDITIONAL_PORTS' and add ports separated by commas In my case: However my privoxy is still in a dead loop, from container LOG: 2021-03-06 10:22:01,606 DEBG 'watchdog-script' stdout output: [info] Attempting to start Privoxy... 2021-03-06 10:22:02,611 DEBG 'watchdog-script' stdout output: [info] Privoxy process started 2021-03-06 10:22:02,612 DEBG 'watchdog-script' s
  6. so as of late VPN works, but I can't get to containers locally SERVER:PORT I can still get to containers through reverse proxy subomain. My delugevpn is behind reverse proxy. also delugevpn logs show privoxy has issues started and goes in a start/stop loop. my stuff is still working, but something seems wrong with container.
  7. Gotcha works now. Thanks for wasting your brain on me today. So swag just uses the container name and it’s own ports. Understood. Sent from my iPhone using Tapatalk
  8. I’m thinking of doing this now but when following the video I don’t see where in 6.9 I can set my xfs encrypted password? Where are the settings for that?
  9. Yes... the same “proxynet” I use for all my dockers behind the reverse proxy. Does it have something to do with the fact that librespeed has a container port different from the host port?
  10. I can't seem to get my librespeed proxy working in swag... I noticed that my host port is 3333 (my preference) and the container port needs to be 80 to work. So I can get to it from UNRAIDSERVER:3333 locally, but through the proxy librespeed.subdomain.com results in a bad gateway. Any idea why? server_name librespeed.*; 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; # enable for Authelia #include /config/nginx/authelia-server.conf; locatio
  11. Yup I encountered that. I got notifications that a login was detected that didn't meet their security standards. Perhaps I'll make a one off gmail account for this purpose. Thanks!
  12. Any free recommendation for the email server? I have a google domain for my unraid server, but I don't want to pay 6-12$/mo for the G suite. How can I get free e-mail hosting on my google domain for the purpose of managing this bitwardenrs docker?
  13. Thank you! Seems like it's working pretty good once you run the authentication script and create the .mounted file! Thanks!
  14. Any reason why jackett seems to always be stopped whenever a new update is available? I can't seem to rely on this container to keep alive.
  15. Thanks @SpaceInvaderOne that worked for me. While we wait for the fix, I found that I lost of lot of time unsuccessfully trying to diagnose what the OnlyOfficeDocumentServer container log was spitting out. Especially the plugin warnings highlighted in yellow and error log path highlighted in red which don't seem to be part of the issue. It seems like the difference in the output of the container log between 6.2 compared to 6.0 are these messages before "Starting supervisor: supervisord." Does this tell us what's wrong? Creating new PostgreSQL cluster 12/main ... /us