Um, where's the proxy? about cultivation HOT 19 CLOSED

did you run cultivation as administrator? potentially a registry edit wasn't made

from cultivation.

did you run cultivation as administrator? potentially a registry edit wasn't made

When I installed and ran Cultivation, it asked to install a certificate, which I did. Nothing happened.

This is all the console shows.

from cultivation.

Try connecting again, and when connected, check your Windows proxy settings to see if they're set.

from cultivation.

Try connecting again, and when connected, check your Windows proxy settings to see if they're set.

I have to decline the UAC prompt when starting the game in order for the setting to actually change.

from cultivation.

Oh! Super interesting, I will take a look sometime and see why that's the case

from cultivation.

Did you test your own build before uploading it? The problem could just be that the build I downloaded was broken, but I'm not building this from source.

from cultivation.

You are welcome to build from source if you’d like, or try a previous version, otherwise I will look into it today at some point

from cultivation.

Same results in the previous version except declining the UAC prompt doesn't change my proxy settings any more. So... this probably is just my problem somehow.

from cultivation.

Started Cultivation from source code (latest commit) and I'm still getting these problems. This... probably is just my problem, though if people understand why this is happening... I'd appreciate it

from cultivation.

If you could provide logs, try some debugging, see if your Windows proxy settings are being set properly upon connecting, etc. that would be super helpful in helping me understand 😄, as I have never encountered this issue myself

from cultivation.

I already posted logs (if console is what you mean) earlier. They weren't for the current commit but I seem to no longer be able to run Cultivation so...

Also for the record, the proxy did get set as http=127.0.0.1:8365;https=127.0.0.1:8365

from cultivation.

This is definitely my problem since even using Grassclipper doesn't work. For some reason the proxy server just... closes instantly. I don't know any reason for this as I've barely messed with proxy servers recently. It just... gets terminated when the game starts, and the game doesn't even start, but my windows proxy settings change correctly? What on earth even is happening any more...
[why do I keep having simple problems]

from cultivation.

Haha, I can't say I know what's going on but those extra details do help. Are you running with yarn start:dev or just via building and then running the exe?

If running with yarn start:dev are there any logs/panics/anything being logged when you try to connect and run the game?

from cultivation.

Haha, I can't say I know what's going on but those extra details do help. Are you running with yarn start:dev or just via building and then running the exe?

If running with yarn start:dev are there any logs/panics/anything being logged when you try to connect and run the game?

I'm doing both.

Well, this doesn't help does it? Sigh, time to build for release...

also I managed to find out that the proxy server being killed was related to a firewall rule I have to block the game from using my internet, weird part is that I enable the firewall rule for my 2.8 genshin and still my 2.7 genshin kills the proxy. Then I have to restart my pc

Okay, I managed to build debug properly:


This is all that really happened.

from cultivation.

I realised that 2.8 is not officially supported and my screenshot was of 2.8, so I tried 2.7.
https://cdn.discordapp.com/attachments/748188072826372299/997613885622325310/2022-07-15_22-20-17.mp4
The video best describes my issue.

from cultivation.

In the instance of that error, disable encryption (via Cultivation OR by setting useEncryption and useInRouting in your server config to false), and make sure HTTPS is off when connecting (both must be done to prevent this issue, I will likely be pushing a change to automatically disable encryption in the configuration at some point)

from cultivation.

Feels a bit weird to not use HTTPS, but it works which is the most important part. Is this an issue that will be fixed eventually or is it impossible to fix?

from cultivation.

It's not an issue to not be using HTTPS, you will still need to enable it to connect to external servers anyways so there is no security implication. I mentioned before that I will be likely adding an automatic server configuration change but that is probably about the extent we'll be taking.

from cultivation.

Alright I see, thanks for the help!

from cultivation.