• Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About akamemmnon

  • Rank


  • Gender

Recent Profile Visitors

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

  1. I ended up changing some network settings in unraid (had IPV4, 6 addresses, and DNS server assignment be automatic) and I haven't had the problem again. not sure if this is the solution, but thats all I got.
  2. If you use a reverse proxy, which ports do you have to open up?
  3. I use swag to route all the traffic to my dockers, but wanted to set up wireguard using a subdomain, is there a way to not have that route through swag? if I put my home IP address it works fine. or can you use swag to point it to the right place?
  4. does any one know what happened to the linuxserver unraid Nvidia plugin? its not available anymore
  5. Hi, I have been running the Riot IM docker for some time and it is great. Now that you created a Element IM docker thats separate, is it possible for us to migrate what we have to that?
  6. Hi, did you ever get this working? I am also using the nextcloud as per SpaceInvader video set up. Did you install it on the proxynet?
  7. im having the same problem, any one figure this out?
  8. Ok so it happened again, the only way I notice this happens is because things like nextcloud and home assistant which I have accessible outside of my network are no longer accessible, but when I am on the local network and I navigate to the IP of my unraid server, its still running fine. But, when I look at my Google Wifi router (which I have used without this problem for years) I notice the device is grayed out and "not connected." when I restart the unraid server, it all works again until the next time... here are the diagnostics, any help would be greatly appreciated tower-di
  9. I have been having this same problem recently. I'm not sure what prompted it. I haven't made any hardware changes. I rebooted, I guess the next time this happens I will pull the diagnostics on my system too.
  10. Hi, I set this up also using that guide. the problem is that when im using bridge mode it works, but when I use a custom proxynet (which letsencrypt is working on) it wont work. so if I want to keep the letsencrypt docker on the proxynet, but have it still work with the open-vpn docker (on bridge mode) I think we have to make some changes to the .conf file that you guys provide. what are those changes? I think this is the problem everyone is having. my ports on my router are open so when open-vpn is on the proxynet it is accessible through my domain, but when its on bridge mode, its not (get N
  11. did you ever figure this out? having the same problem
  12. did you ever figure this out? I'm having the exact same problem now
  13. server { listen 443 ssl; listen 8448 ssl; server_name your.domain; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver valid=30s; set $upstream_app matrix; 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 /.well-kno
  14. so I was getting federation according to the tester, but it wouldn't communicate with those severs. after talking to the support people and reading other webpages, I found out that my .conf file in letsencrypt needed this line: location /.well-known/matrix/server { default_type application/json; return 200 '{"m.server": "yourdomain.com:443"}'; add_header Access-Control-Allow-Origin *; maybe it will help someone else. thanks for the reply!