• Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

HojojojoWololo's Achievements


Newbie (1/14)



  1. Actually, I have no clue since I have not tried that and because I stopped using Matrix/Element, I won't try it any time soon. Sorry
  2. In my defense, the post is almost two years old (so it's pretty outdated) and it took me a days-long odyssey to get it to work, too. I mentioned that here, though, so you could have been forewarned But I can absolutely understand your annoyance and when an update of Jitsi failed last year, I decided to get rid of it cause the setup was so painful.
  3. Hi guys, I need some help, too, cause I can't figure out what to do even after some hours of research. Problem: I am using Wireguard for some months and everything works fine since everyone who connects via Wireguard is supposed to have complete access to the LAN of the server. But on my server, there is one docker-container which I allow some friends to have access to. For that purpose, I used an OpenVPN container since I was able to restrict the VPN access to just one specific container (within the OpenVPN config, I was able to restrict certain users to certain IP mappings within the server's docker network). Now the OpenVPN docker is EOL for Unraid and coincidentally, my OpenVPN setup broke. My problem: how can I achieve to set this up via Wireguard in Unraid? I do not want those people to access my whole server/LAN/... but only one specific docker container (IP is only "fixed" by the boot sequence of the docker containers - not by assigning a fixed IP to the container itself). Hopefully, someone has some tipps for me
  4. No, you cant. The mobile game is a completely different product and technically has nothing to do with the console/PC version.
  5. Yeah, it seems like it works without any problems, it just looks ugl y when opening the log 😅 Thanks for your reply 😀
  6. But I still got some problems here. The biggest one: Rocket.Chat isn't able to connect to the Rocket Chat Cloud. I set up an account and had to register it manually - the link for the online registration with my Rocket Cloud account didn't work. When I want to connect to the cloud services and click on "the sign in button within my Rocket Chat server, I am redirected to a cloud.rocket.chat uri to login which returns this error: I tried to click sync - rocket chat even tells me that the sync was successful. But the error message is generated again when trying to sign in. I logged into cloud.rocket.chat and removed the server from my workspaces. I also registered that I had some kind of dummy second workspace called Your Workspace registered. I deleted this one, too. In a second step, I was able to register again - with the online token. I was directed to the correct URI and was able to login with my credentials. Another error message appeared: I also tried to delete the cloud sync info from my database using the MongoDB containers console mongo use rocketchat db.rocketchat_settings.remove({"_id": “Cloud_Workspace_Id”}); db.rocketchat_settings.remove({"_id": “Cloud_Workspace_Client_Id”}); db.rocketchat_settings.remove({"_id": “uniqueID”}); But there still is the "associated with a different Rocket.Chat Cloud account" error. Is there anyone who has a solution for this problem?
  7. I think I found a solution. Had a problem with the authorization while installing Rocket.Chat, too. After reading that working with a MongoDB replica set requires both account and keyfile, I started a terminal and mounted into the MongoDB appdata folder: cd /mnt/user/appdata/mongodb Then I created a keyfile and set read/write permissions with the following two commands: openssl rand -base64 741 > mongodb.key chmod 600 mongodb.key Afterwards, I edited to mongodb.conf file in the MongoDB appdata folder and added the direction of the keyfile: security: authorization: enabled keyFile: /data/db/mongodb.key Now the enabled authorization works for me 💪😁
  8. Don't lose hope. I think you nearly got it. Reminds me of my status some days ago 😁 Try what I posted above: in your homeserver.yaml put client and federation in 'inverted commas' - port: 8008 tls: false type: http x_forwarded: true bind_addresses: [''] resources: - names: ['client', 'federation'] - port: 8448 tls: false type: http x_forwarded: true bind_addresses: [''] resources: - names: ['federation'] Also set database direction to data/homeserver.db database: name: sqlite3 args: database: /data/homeserver.db Additionally, try to add a TCP TURN URI (remember to forward port 3478 to your server for both protocols): turn_uris: ["turn:bridge.mydomain.xyz:3478?transport=udp", "turn:bridge.mydomain.xyz:3478?transport=tcp"] And finally, remember to change your secrets and keys since you shared them with us. That's not the meaning of shared_secret 😉😁 I hope that you get that thing running. If it doesn't help post your turnserver.conf please (without the shared secret of course).
  9. Yep, the tutorial kinda works with a few adjustments. But since I had to work my way through multiple posts and other sites I would love to spare you the pains. My initial setup was an unraid server running Swag (since the Letsencrypt docker wont be supported anymore in the future due to naming rights - spaceinvaderone made a great tutorial how to switch from the Letsencrypt to the Swag docker). Yinzer's tutorial for the Letsencrypt docker still seems fine, though you really should use the Swag docker instead. Furthermore, Jitsi was already up and running when I started to install Matrix (thanks to spaceinvaderone, again 😄), so I will skip that part. If you have to set up a reverse proxy (be sure to use the Swag container instead of the Letsencrypt container) or want to switch to Swag, the spaceinvaders videos are really helpful. My adjustments to @yinzer's Matrix setup: Setting up Swag (formerly Letsencrypt) matrix.subdomain.conf - thanks to @akamemmnon for his config 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 your.unraid.server.ip; 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-known/matrix/server { default_type application/json; return 200 '{"m.server": "yourdomain.com:443"}'; add_header Access-Control-Allow-Origin *; } } Make sure to change your.unraid.server.ip to your unraid server's IP adress and yourdomain.com to your domain name 😁 Since Riot was renamed to Element, there is a new container so we will use that one instead of Riot and have to adjust the Swag configuration file. element-web.subdomain.conf server { listen 443 ssl; server_name chat.*; include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver valid=30s; set $upstream_app element-web; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } } Install Matrix and configure it according to yinzer's tutorial. Adjustments: Setting up Matrix homeserver.yaml under "listeners" in the "# Unsecure HTTP listeners: for when matrix traffic passes through a reverse proxy" section: - port: 8008 tls: false type: http x_forwarded: true bind_addresses: [''] resources: - names: ['client', 'federation'] - port: 8448 tls: false type: http x_forwarded: true bind_addresses: [''] resources: - names: ['federation'] Make sure you respect the .yaml syntax - that's what created the syntax errors of @lewisd19, @jafi and @l2evy. No tabs, just spaces! Additionally, the resource names have to be commented with inverted commas: 'text'. The examples over this section can help you with this. If you use the standard SQLite database, make sure you changed the database's direction - thanks to @spyd4r for your input. database: name: sqlite3 args: database: /homeserver.db SHOULD BECOME database: name: sqlite3 args: database: /data/homeserver.db turnserver.conf Delete the first line which says "lt-cred-mech" since we use "use-auth-secret". Also think about adding the pidfile and userdb infos yinzer posted in his tutorial. My turnserver.conf looks like this: use-auth-secret static-auth-secret=YOUR-STATIC-AUTH-SECRET realm=turn.bridge.yourdomain.com cert=/data/bridge.yourdomain.com.tls.crt pkey=/data/bridge.yourdomain.com.tls.key dh-file=/data/bridge.yourdomain.com.tls.dh cipher-list="HIGH" pidfile=/data/turnserver.pid userdb=/data/turnserver.db Setting up Element-Web (based on @yinzer's tutorial for Riot Chat) 1. Before we start, we need to manually create the config path and pull in the default config. So open the terminal/SSH to your server. 2. Create the config path by executing mkdir -p /mnt/user/appdata/element-web/config 3. Download the default config by executing wget -O /mnt/user/appdata/element-web/config/config.json https://raw.githubusercontent.com/vector-im/element-web/develop/element.io/app/config.json 4. In Community Applications, search for `element-web' by vectorim 5. Set the `Network Type` to `Custom: ssl proxy` 6. Set the `Fixed IP address` to `` (or whatever) 7. The rest of the settings should be fine. Create the container and run it. Now lets edit our Element config. It's a JSON file, so make sure you respect JSON syntax 1. Edit /mnt/user/appdata/riot-web/config/config.json 2. Change 'default_server_name' to "default_server_name": "bridge.yourdomain.com", 3. Insert your domain to the 'roomDirectory' "roomDirectory": { "servers": [ "bridge.yourdomain.com", "matrix.org", "gitter.im" ] } 4. Add the following lines in the config: { "jitsi": { "preferredDomain": "meet.yourdomain.com" } }, Caution: Using a Jitsi server with enabled authentification doesn't work with Element! And this should also be noticed: Jitsi Setup Just follow spaceinvaderone's instructions in this video. But for setting up a working Matrix synapse and the Element-web container, that should be it. @yinzer Feel free to update your initial post with this adjustments 😃
  10. Thanks for the tutorial and all your work @yinzer - altough it could use a little update. Finally, I got Matrix working... after nearly 3 days of work and reading this thread as well as various other sites again and again😀 Element-Web is also connected now and I was able to create a useraccount on my matrix synapse. Federation and integrations manager seem to work, too. *edit* Problem solved. Stupid mistake because of lack of sleep. Night shifts ^^ But the log of my Matrix Container shows the same "Socket: protocol not supported" errors @xthursdayx described in this Github post. Must be the TURN-part of the Matrix container. @xthursdayx: did you find a solution for your problem?
  11. Nice workaround. Thanks for sharing your thoughts, it seems to work so far. But if I remember it right, the Letsencrypt container has to be added to the jitsi docker-network each time the Letsencrpyt container restarts, correct? I seem to recall that the docker cointainers are only able to save one network.
  12. Sound like an interesting idea. +1 demand unit for your proposal and +1 demand units for the demand of the threadstarter.
  13. Hey Jones, as you can see in my signature, I switched to a Ryzen 2600 and the server runs like a charm - despite some config-errors during the setup (first unRAID setup ;). The CPU's cores are only fully utilized when I run foldingathome - even during three streams with downcoding via Jellyfin, the max. CPU-usage is at about 40-60 percent (at the moment no GFX card). Max. CPU-Temp. is around 37°C (~30 in idle) with the boxed cooler. Planning to upgrade the server with a GFX-card and watercooling in the future though. The SSD-cache seems crucial to me, otherwise copying data to the server would definitaly be to slow for me. The SanDisk nVMe-SSDs get a little warm on a high workload (about 45-55°C) but thats just during intense copying-sessions. Picking the WD-HDDs was a good choice, too - no problems, even my 5-year-old WD Red 3TBs from my old FreeNAS still work fine without SMART-errors or other problems. Case keeps the machine very silent. And finally, I am very happy about the two Gbit-LANs. Makes lots of stuff easier. The IPMI-feature I only used for the setup... made things a little bit easier but since I never used it again, I'd say the feature is rather nice-to-have than a must-have. If you have any other questions, just PM me. Best wishes.