HurracaineIke

I got it! I was previously sending the unzipped folder over the network to my server which I think caused some weird permissions issues. Unzipping the folder in the destination folder solved it!

Yeah, that is what I am doing but no luck unfortunately :( it's coming as a zip file from my friend's computer and I have unzipped it, moved it onto my server, and followed all these instructions multiple times and it doesn't want to stick.

Did you ever sort this out? I am having the same problem (seey post above)

Did you have to do anything special when moving your saved world into the docker container? I have seen a bunch of descriptions on how to move the server over from a user to a server but I am having an issue. I copy over the alphanumeric folder in it's entirety to my server and add it to the ../0.10.0/Worlds folder, I delete the other world that was in there, I ensure that the ServerDescription.json is updated with the matching WorldIslandId and I start the server. A new world is created and the ServerDescription.json is overwritten with this new world ID. If I reboot the server that new world continually persists. It's only when I try to inject my world that I am moving over that it doesn't work. I even tried using the new WorldIslandId to name the folder that I am moving over and tried updating the WorldDecription,json to match as well, thinking there were some other links somewhere that weren't working.... but that didn't work. I made sure the ownership for the files and folders are the same and made sure all users have full read write and execute permissions on the folder and all its contents.... Any ideas?

Update: it seems port 3478 may also need to be opened. Need to to more testing to verify, but remote connections are possible now. Port 7777 tcp and udp should be opened when the docker is on a custom network and using direct connection. Verified using a vpn for external connections. Just checking with friends to see if they can join. All other parameters except for the ‘UseDirectConnection‘ were left as default. Update: Friends can join. I think the missing part for my setup was simply enabling TCP port 7777 alongside the UDP for ports 7777 and 7778

So I have this kinda working for windrose, but having some networking problems. I am trying a direct connection method and I am able to connect to a world from my PC when the container is in host mode, but when I go to bridge or custom network and have the 7777 and 7778 ports mapped in the container, and the GAME_PARAMS variable set to -MULTIHOME=0.0.0.0 -PORT=7777 -QUERYPORT=7778 , I cannot connect on my home network. I get to the loading screen and then a few seconds later I am booted back to the main screen. I have tried messing around with the ServerDescription.json to have my server IP address in every possible combination for the P2PProxyAddress and DirectConnectionProxyAddress variables, but it doesn't want to work. I looked at Wireshark and it looks like when my PC reaches out to port 7777 I get a bunch of reset responses back: It looks like it tries at two different ports and then gives up. In every scenario, nobody can join remotely either (even though I have a port open on my router pointing to my server). Would this be just a plain and simple networking issue or perhaps an issue with properly assigning the access to specific ports that the container needs?

Thinking about it more and I definitely think point 1 was the solution. When you make the request to go to your domain it will be https (port 443) and pretty sure pihole takes that right away before it can get to your router (which would forward to port 1443). So then the request is going to your server at port 443 (instead of 1443) and thus you cannot connect to nextcloud directly. I couldn't find a way in pihole configs to forward 443 requests to 1443 with DNS records so setting swag to 443 fixed the issue if I recall correctly.

@bucketphobia Super late response. Sorry I never come on here. I did actually figure it out eventually, however I can't recall off the top of my head exactly how. Pretty sure it was one of two things (or both): 1. Changed my SWAG instance to run on port 443 instead of port 1443 - something funky was going on there, I think it was something to do with Pihole not working with DNS records to a different port. 2. Added my unraid server IP address to the resolver.conf file in /mnt/user/appdata/swag/nginx (Although I think this was actually from me trying to get hostnames on Pihole...fairly certain it was solution 1)

To start, I am very new to all this so probably just have some misunderstandings of how things work. Like a lot of people, I used SpaceInvader One's tutorial on getting my unraid server setup to run nextcloud behind SWAG with my connections routing through cloudflare. Everything works great through that path internally and externally, however my issue is when I am on my LAN and try to upload files to my nextcloud, I am limited to the speeds through cloudflare/my ISP - windows performance monitor is showing 8Mbits/s send, unraid shows peaks of 60Mbits/s receive on the NIC. I tested the LAN speeds from my desktop to my server using IPerf and am getting my expected 900+ Mbits/s speeds (yes, Mbits/s not MB/s) Here's a breakdown of my setup: Unraid 6.10.3 Linuxserver's SWAG docker Linuxserver's Nextcloud docker Linuxserver's MariaDB docker selfhoster's Cloudflare-DDNS docker Spant's Pihole Docker I have port 443 access turned off on my unraid server and connect to it locally only over port 80 (http). My SWAG uses unraidIP:1443 and unraidIP:180 My nextcloud uses unraidIP:444 mariaDB uses unraidIP:3306 Pihole is on a static IP in the same subnet as unraidIP, let's call it PiholeIP. I have my own domain from google domains linked to cloudflare. Cloudflare has a 'A' record for my public IP (which is updated using the Cloudflare-DDNS docker I believe) and then I have a CNAME pointing to that and I am able to successfully connect to my nextcloud using that xyz.domain.com. Both the A record and CNAME record are proxied on cloudflare (it was the only way I could get it to work when initially setting it up). SSL/TLS is set to Full (Strict) and I enabled HSTS. When I connect to xyz.domain.com the certificate is being provided by cloudflare (so not LetsEncrypt). My router forwards port 443 to SWAG at unraidIP:1443. I do not port forward port 80. SWAG is routed through cloudflare (through the config files I believe?). SWAG is then connected to my nextcloud. I have nextcloud and swag on a custom docker network ('proxynet') so they can talk to each other without having to dig deeper into config files. I did change SWAG to use 'Modern configuration' (e.g. TLSv1.3) instead of 'intermediate configuration' in the ssl.conf as I don't need older browser support. This is where my knowledge gets fuzzy and I'm kinda just throwing mud at a wall at this point...I think I have to setup a 'split-brain DNS'... I tried changing my nextcloud to unraidIP:443 and then using Pihole (which is setup and working nicely right now) to create a DNS record that directs me to unraidIP, however when I do this I get "“Privacy error: Your connection is not private” (NET::ERR_CERT_AUTHORITY_INVALID)" If I try going to unraidIP:443 locally, my router forwards that request to SWAG (port 1443) which then overwrites(?) that request to xyz.domain.com and sends me back through cloudflare. So I have not tried setting nextcloud back to port 444 and using port 443 for SWAG as I believe I would get the same result anyway? Which leads me to believe this is all a problem with cloudflare certificates or SWAG. I don't know if it's possible to get the certificate from cloudflare and install it somewhere so that local access is allowed (since my SSL/TLS is set to Full [Strict] ) or if there's something in the SWAG config that I can edit so that it sends requests through cloudflare only if it is a request from outside the network? My router is a basic D-link one so I don't have much in the way of firewall rules (that I can find) I seem to only be able to allow or deny WAN to LAN / LAN to WAN requests there. Plz send help.

D'oh. Noobie mistake - my share had export set to 'no' under SMB security settings. Changing it to 'yes' solved my problem.

@itimpi I have an unraid user setup with right to that share. I use the unraid account credentials to try to sign into the share when mapping and it does not work. I have also tried setting the share to public and still cannot access it.

Hello! I just setup a new unraid server (6.10.3) using a trial license. First time doing this. Hopefully I am just doing something simple wrong. I cannot get into my shares to copy files over from Windows 10 Home (21H2, 19044.1766), I keep getting error 0X80070035 (The network path was not found) when I try to map the drive. I try mapping "\\Server.IP\Share.Name" and signing in with a new user account (not root) that has read/write access to that secure share. I am able to access the unraid GUI, I am able to get to "\\Server.IP" or "\\Server.Name" in windows explorer, but it just says the folder is empty. I tried: I created a new user share "BackupStorage" and a user account (with read/write access) to access that secure share. Ran 'Fix Common Problems' plugin (extended test) in unraid but it says nothing is wrong. I have tried adding my credentials manually as well as deleting all unraid credentials in windows credential manager, neither has any effect. I realize it's not best practice, but just for testing I had enabled SMB v1 in windows features, didn't do anything (I disabled it again). Turning on NFS in unraid didn't do anything (I turned it back off). My 'Workstation' and 'TCP/IP NetBIOS Helper' services are enabled and running. My network is set to private and "network discovery" and "file and printer sharing" are set to on (turning off password protected sharing does nothing too, so left that on) I cannot access gpedit.msc from run (Windows Pro feature?). tried to connect while windows firewall was disabled, no change. I am signed into my PC with a windows account so not sure how to make an unraid account with the same credentials as that, therefore I have not tried that fix yet. I have read other threads here in depth but nothing is working for me. I have attached my diagnostics. Please let me know if there is any other information that would be helpful. I'd really like to get this working! gollumnas-diagnostics-20220621-0815.zip