Coolsaber57

Members
  • Posts

    111
  • Joined

  • Last visited

Recent Profile Visitors

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

Coolsaber57's Achievements

Apprentice

Apprentice (3/14)

7

Reputation

  1. Do I need MariaDB or MySQL, or would a Postgres DB work? Edit: apparently it won't work, so I created a MariaDB. Does anyone know if you can merge multiple people to the same "Person"? I see a bunch of the same people as separate. Also, I don't think the Public Endpoint thing is working - when I create a public link, it still shows my internal IP address.
  2. Would you mind posting the config from NPM? I'm using SWAG and am having the same issues, but cannot get the site to show through using the sub domain.
  3. I'm struggling with this as well - set it up with the same proxy.conf file provided by SpaceinvaderOne, with the exception that SWAG wouldn't boot unless I removed what it called a duplicate, which was the: proxy_redirect off; Once I removed it, SWAG booted. I can access OnlyOfficeDocumentServer via internal IP address, but not my domain name (shows an NGINX error "400 Bad Request" when I try to navigate to it, and a bad health check in Nextcloud). Can someone post a working NGINX proxy.conf so I can see what I'm doing wrong?
  4. I might be a little confused as to how this plugin works. I'd essentially like to move some stuff from a drive that's nearing capacity to 3 other drives. However, when I attempt to run this, it just puts it all on one drive, instead of "Scattering" it across the drives. Any advice?
  5. Hey all, I'm trying to access Home Assistant Core via the lets encrypt docker, have updated the proxy.conf sample they have for Home Assistant with the new container name, as well as the port I mapped in. I can access the page via my subdomain I set up (shows the HA user name and password prompt), but when I attempt to login, it just shows the HA symbol and the "refresh" button. Here's the proxy.conf: # make sure that your dns has a cname set for homeassistant and that your homeassistant container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name ha.*; 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; 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 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app Home-Assistant-Core; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } Is there something I"m doing wrong? I also set the external URL in the Home Assistant .yaml, but no dice. Edit: I always seem to find the solution right after I post in this thread. For future reference, if anyone needs the config for this, you need to add a section for /api. Here's the updated (working) config: # make sure that your dns has a cname set for homeassistant and that your homeassistant container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name ha.*; 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; 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 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app Home-Assistant-Core; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } location /api/ { resolver 127.0.0.11 valid=30s; set $upstream_app Home-Assistant-Core; set $upstream_port 8123; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header Host $host; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } }
  6. I've had this set up for a few months and love it. However, I can't seem to access the admin page. If I replace the "Admin Token" with a new one in the docker config, and subsequently enter that value into the Admin page password, I get an Invalid Token error. Am I missing something obvious?
  7. OK, I had this all working great on my phone and laptop some months ago. But today when I tried it, I was able to connect fine on my phone, but could not access the internet. I could access my unraid server, so I know it's working, and i have "remote tunneled access" selected as the type. I'm not sure if some update borked it, but is there anything I'm missing? Is there a known issue that is preventing internet access? Edit: resolved my issue by adding my router's IP address to the Peer DNS server section
  8. I was reading on reddit that some dude solved this by using Postgres instead of MariaDB, but I'm having trouble creating a user in Postgres to test this: https://old.reddit.com/r/unRAID/comments/fy7na5/nextcloud_login_and_navigation_extremely_slow/ Are you able to try this? Edit: Fixed! Ok, I don't know why but the cause of the slowdown was MariaDB. Following the above reddit post, I downloaded Postgres 11 and set up the db using the following commands: su - postgres createuser --interactive --pwprompt [enter desired name e.g. nextcloud] [enter desired password] [confirm desired password] [Superuser?: n] [create databases?: n] [create more roles?: n] createdb nextcloud psql GRANT permissions ON DATABASE nextcloud TO nextcloud Then selected Postgres on the Nextcloud setup page and entered the details. The page actually loads like normal, finally.
  9. Hey there, did you figure out what your issue was? I am having the same problem
  10. OK this is driving me nuts, I cannot figure out why Nextcloud is so slow. It takes about 30+ seconds to load each page, accessing it from inside my own network. To try and solve this: I wiped my entire nextcloud installation, including all folders and appdata, even the database in MariaDB. I then created a DB and installed the container fresh. It completed setup, but it's still slow as molasses. The CPU/Memory do not even blip and all other containers function fine, so I know it's not a performance issue. The Container log is fine - no errors. The only errors I see in Nextcloud's "logging" tab in Setttings are: I tried googling and the only thing I came across is bruteforce protection, but I checked the DB table and it's empty, so that's not it. Can anyone help me figure out what the issue is? I've seen a few other posts that mention this without a resolution.
  11. Yep, I looked at the container logs - no errors at all. Trying to dig into Nextcloud's UI to see if there is additional logging that will tell me what's going on. It's just weird, it only happened recently, so I thought it was an update.
  12. Is anyone else having performance problems with NextCloud? It's been fine for me until lately. My Container is up to date and I've updated NextCloud via the UI, but it takes forever to load the Web UI. Did something change recently? All my other containers load normally.
  13. I have an odd issue - I've been able to successfully connect to my server using the "Remote Tunneled Access" option on my phone without issue. I created another peer of the same type to connect my Windows laptop, but the only way I could get it to work was to un-check the "Block Untunneled traffic (kill-switch)" option. This seems to add "128.0.0.0/1" to the allowed IPs. Does this mean that it's not routing all my traffic through the VPN? Is there some configuration I need to fix?