ProAm500

Members
  • Posts

    9
  • Joined

  • Last visited

ProAm500's Achievements

Noob

Noob (1/14)

0

Reputation

  1. So it looks like there were some artifacts from copies, migrations, etc. I went ahead and deleted the offending share and looks like everything is safe.
  2. I honestly, I have no idea, but my best guess was during some data transfer or copy at some point. I have moved, replaced, and upgraded disks at a couple different points in the 4ish years that I have had this server online. I guess I can try to do a compare of those two directories to see what's exactly in them.
  3. Sorry for resurrecting this old thread, but I am have the problem of having a share called "disk2" /mnt/user. In that /mnt/user/disk2 directory is the folder Vids, where I put all my video media. I also have a share in /mnt/user called Vids with the same content. Basically looks like this: /mnt/user/disk2/Vids /mnt/user/Vids Am I ok to delete the /mnt/user/disk2/ or will that delete the Vids directory and all the content contained in it? studio-diagnostics-20220127-1328.zip
  4. were you able to get this working? can you share in details what you did?
  5. Still somewhat of a unraid n00b so hopefully someone can help me out. I'm trying to accessing koel outside of my local network via domain and subdomain that i have created . I have success using spaceinvaders instructions for emby, sonarr, etc using the templates and doing the necessary edits that have been included in the proxy-conf folder for letsencrypt. There isn't a template for koel and im having some issues getting access from outside my network. Can you guys take a look and see what i might have wrong in my config? I can "connect", but its unsecure and only a blank white page shows up. ( i currently have the koel docker shutdown until I can figure out whats going wrong ). server { listen 80; server_name <subdomain>.*; return 301 https://$host$request_uri; } server { listen 443 ssl; listen [::]:443 ssl; server_name <subdomain>.*; 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_koel binhex-koel; proxy_pass http://$upstream_koel:8050; proxy_set_header Range $http_range; proxy_set_header If-Range $http_if_range; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; }
  6. Spoke to soon. After clicking the generation link a bunch of times, I was able to get logged in.
  7. My login name for SurfShark is my email address so obv. an @ in the username. Also, when I download the .ovpn a username and password is generated that does not contain any special or illegal characters, so not sure what else to try.
  8. Also getting the AUTH: Received control message: AUTH_FAILED message trying to connect to SurfShark VPN service and not able to connect to the docker. I have downloaded and uploaded the OpenVPN files to /mnt/user/appdata/binhex-delugevpn/openvpn and entered the user and pass that is generated by SurfShark. I have also tried my login creds. that I created for SurfShark and still no luck. Not sure what else to do.