#System Error
20 messages · Page 1 of 1 (latest)
You haven't configured your server to be accessible on the network, so no connection logs because you aren't connecting to it. You're getting this error for the same reason as "the server is not running"
Also if you aren't playing from the vm, you have no need at all to have cultivation on it since you're just running Grasscutter on it
I downloaded Cultivation on it for good measure, I know it's redundant.
Can you refer me to something relating to this?
There are many posts, the short of it is you need to change the accessAddresses (both of them) to the local ipv4 of the host machine, then you will connect to that local ipv4 instead of localhost
As the host and connecting machine are on the same network there is nothing else needed
There's an entry in the pinned thread of common issues called "Playing with friends / 4206" which describes the process, if you just replace the hamachi ipv4 with your machine's local ipv4 instead.
Your device either isn't connecting to the server properly, or your encryption settings are incorrect. Check #1083482155243544656 message for more information.
Alright, I've followed your instructions here and changed both the Server and Game "accessAddresses" to the IPv4 of my PC, I still got the same error. I'm assuming that I'm doing this correctly; however, I could be doing it wrong. I used run (windows key + r), typed in "cmd" and opened Command Prompt. I ran the "ipconfig" command and copied my "IPv4 Address" from the "Wireless LAN adapter Wi-Fi" section and replaced the "accessAddresses" to it.
I tried this using "Toggle Encryption" checked and unchecked on my VM and checking/unchecking "Use HTTPS" on my PC, respective to the setting I had on my VM.
I tried both "localhost" with port "443" on Cultivation on my PC as well as my IPv4 with port "443" but neither of those worked.
The proxy on Cultivation is working fine, there are no issues there. Windows manual and automatic proxy settings in Windows Settings are disabled for both my VM and PC.
There's only three issues I could see that could probably fix this:
- The first issue is simply that I'm doing something wrong with changing the "accessAddresses" in the config file.
- The second issue is that I'm not using "hamachi," but you said that there is nothing else needed.
- The third issue is the Grasscutter version (1.5.1-dev) that I am using since in the console, it says "Game version: 3.4.0" even though the version of Grasscutter I am using is supposed to be for 3.5.0, see: #resources message. I personally do not think this is an issue since I've seen another thread with the same "Grasscutter version" and "Game version", see: https://discord.com/channels/965284035985305680/1086823771077353523, message: #1086823771077353523 message, in which they eventually were able to resolve their issues and log in perfectly fine.
Sorry for the walls of text lmao.
You don't need hamachi, your problem was using your PC's ipv4. Your PC is not the host, so you can't use its address. You must use the ipv4 of your host, the VM
Ah, I see. I thought you meant "host" as in host PC since whenever using a VM, the PC running the VM is normally called the "host."
Also yes, the jar says 3.4 but it is for 3.5. You can tell because 1.5.1 is not a real Grasscutter version, it's made up by the person who built the 3.5 jar
The pc is the host for the vm, but the vm is the host for the server
Yep, when you said, "host machine," I confused the two. I will go and see if your solution works, this time using the VM's IPv4.
Well, at least I'm not getting a "System Error" message anymore. Now I'm getting a "Connection failed, try again later" error when attempting to log in.
You must disable encryption in your Cultivation settings and restart your server. Refer to #1020898384317513738 message for more information.
Cultivation proxy is being turned on, Proxy settings are being set to "Manual." Cultivation's "Server IP" is set to my VM's IPv4. "Use HTTPS" is unchecked, "Toggle Encryption" is unchecked. Both of the "accessAddresses" are set to my VM's IPv4.
Still getting this issue, "Connection failed, try again later."