Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

3 Neutral

About spyd4r

  • Rank
    Advanced Member


  • Location

Recent Profile Visitors

589 profile views
  1. Is anyone able to get a VM running on unraid able to talk to netboot.xyz? I have it all setup as documented in my Unifi configuration, I just get no pxe boot from a VM. edit: pxe boot happened once, and it's gone again.. it's like I am not getting the DHCP request. edit 2: I figured it out, with Unifi USG, I had to add the following dhcp options NAME: code_93 CODE: 93 TYPE: Unsigned integer 16
  2. Exactly. Just stay on stable and wait for official releases then.
  3. I'll show you my matrix.subdomain.conf file server { listen 443 ssl; listen 8448 ssl; server_name bridge.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver valid=30s; set $upstream_app; set $upstream_port 8008; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_set_header X-Forwarded-For $remote_addr; } location ^~ /_matrix { proxy_pass; } location ^~ /_matrix/identity { proxy_pass; proxy_set_header Host $host; proxy_set_header X-Forwarded-For $remote_addr; } } While we're at it, in regards to your port forwards on your router, how do you have it configured? Are you using cloudflare also? I noticed a few things needed in regards to configuring DNS at cloudflare for federation to work properly. also, in regards to turnserver.conf. I think you added pidfile=/data/turnserver.pid userdb=/data/turnserver.db did you also add the no-cli?
  4. 1 thing i see right off the bat.. database: name: sqlite3 args: database: /homeserver.db should be database: name: sqlite3 args: database: /data/homeserver.db other then that the only differences between yours and mine is the listeners, I have mine setup a bit diferently. listeners: # TLS-enabled listener: for when matrix traffic is sent directly to synapse. # # Disabled by default. To enable it, uncomment the following. (Note that you # will also need to give Synapse a TLS key and certificate: see the TLS section # below.) # - port: 8448 tls: false type: http x_forwarded: false bind_addresses: [''] resources: - names: [federation] compress: false # Unsecure HTTP listener: for when matrix traffic passes through a reverse proxy # that unwraps TLS. # # If you plan to use a reverse proxy, please see # https://github.com/matrix-org/synapse/blob/master/docs/reverse_proxy.md. # - port: 8008 tls: false type: http x_forwarded: true bind_addresses: [''] resources: - names: [client] compress: true - names: [federation] compress: false Can you paste your turnserver.conf? (remove the secret)
  5. if you want to send your conf file for matrix privately to me or paste here and make sure you remove anything sensitive. perhaps we can give you a hand.
  6. I got a locally run dimension server up and running, noticed that was still in your todo. Let me know if you need assitance putting that together.
  7. in regards to the pid file edit /data/turnserver.conf, add the following and restart pidfile=/data/turnserver.pid userdb=/data/turnserver.db perhaps, @yinzer should add this to the original post. I believe you can set "no-cli" in turnserver.conf as well to remove the other message. reference: https://github.com/instrumentisto/coturn-docker-image/issues/13
  8. if you don't have ipv6 make sure you don't have it listed ['::1', ''] or whatever it looked like, make sure you set it as TeddyTux mentioned above... Took me a couple minutes to notice this.
  9. spyd4r


    +1 would also like the ability to have it configured easily for authentication on rooms.
  10. I love being able to easily manage docker and vms right from the GUI.
  11. I had the same issue as well. Didn't pay too much attention as I had to drive to work and was fine when I checked later in the day.
  12. yeah, unfortunately I use it to write my Security Footage for my cameras to.
  13. twice now, i've had all my shares disappear.. no idea what's wrong or what i've changed. basically everything stops working as you'd expect. Reboot fixes it though. I was up 3 days previously since the patch no problems, not twice today i've had this issue. This diagnostic file is after they disappeared, and after array manually stopped but not yet restarted, server.lan-diagnostics-20191015-1822.zip
  14. I had my Plex DB corrupt as well. On a cache drive, on rc4.. Which I don't believe should ever happen.. I think it may have happened during the upgrade of the container overnight though.
  15. Can confirm with all 6.7.2, had appdata on array and it corrupted immediately and repeatedly. Switched to cache disk and no issues.