#Cant connect to localhost

92 messages · Page 1 of 1 (latest)

low briar
#

It keeps saying version mismatch even though i have 3.2 resources

image.png
#

well I guess you don't have the 3.2 server

low briar
mild junco
#

As said above, what resources your server uses has nothing to do with what version the server is for

#

The JAR alone determines what version the server is for.

#

You're using a jar for 4.0, so you're on 4.0 regardless of using 3.2 res. You can find a full 3.2 Grasscutter build in #resources

low briar
#

oh....

#

right

#

it works now thanks

low briar
#

well almost now it keeps saying error 502 💀

low briar
#

i alr did

#

are you using "use https" option ?

#

no

#

encryption enabled?

#

no

#

has the server started properly?

#

it says done so i guess yes

#

provide console logs

#

wait

#

i acc made it worse i think if i try to run the 3.2 jar it randomly opens 4.0

low briar
#

i did that aswell

low briar
#

yep

#

its on 3.2

#

provide console logs

#

dont have rn

#

but it didnt give any errors

#

send when you can

#

its in the gc path in a logs folder i think

#

it keeps glitching

#

so im gonna re unpack the 3.2 thing

low briar
# low briar

weird, are you using two proxy software at the same time?

#

uhh i dont think so

#

do you use cultivation?

#

yes

#

hmm maybe you're using encryption and you don't know, please check again when possible

#

its disabled

low briar
#

this means that the server has started right?

image.png
#

yes

#

it doesnt log anything

#

then you're not reaching the server

#

do you have "use internal proxy" on?

#

yes

#

are you connecting to localhost 443?

#

i guess you are since it's default address, just in case

#

maybe try changing the port in config.json of gc

#

and connecting to it

#

i have to go, wait until i come back or thoronium goes online

#

i got 2 of those for some reason

image.png
low briar
#

if it doesnt then ill just wait

low briar
low briar
# low briar

try renaming normal config.json to config.json.bak and using this one as config.json

#

will it automatically use the first one for config or do i have to rename to config.json

low briar
#

umm

#

there are 3 configs rn

#

what

#

i just realized that in the first config.json you sent the http port is 442

#

ye i changed it

# 
"http": {
      "bindAddress": "0.0.0.0",
      "bindPort": 442,
      "accessAddress": "127.0.0.1",
      "accessPort": 0,
      "encryption": {
        "useEncryption": true,
        "useInRouting": true,
        "keystore": "./keystore.p12",
        "keystorePassword": "123456"
      },
#

you told me to right

#

oh

#

true

#

lol

#

did you try to connect with cultivation t o that one

#

i forgot i told you to do that before lmao

low briar
#

just use this one

#

and use port 443 in cultivation

#

oh

#

that worked

#

it also showed up in logs now

#

ty

low briar
#

oh i see

#

have fun

#

well ty for helping me fix it

#

np buddy

mild junco
#

Two configs: one for normal proxies, one for Cultivation

#

For anyone else, you use it by renaming config.json to anything else or deleting it, then renaming the config for Cultivation to config.json. It's simply a difference of useEncryption and useInRouting settings being false instead of true though

low briar
#

Didnt it said server 4.0.0
But you have 3.2.0
I guess you need 4.0.0

low briar