#External Server Issues
57 messages · Page 1 of 1 (latest)
Still can't find any answers, any information or help would be appreciated, I'll even be willing to compensate anyone who can help me get it working depending on the amount of help given
are you using velocity, waterfall, or paper
paper @ornate shore
did you add all 4 startup flags correctly
I think so
Add all of the following flags: -Dminecraft.api.auth.host=https://authserver.mojang.com/ -Dminecraft.api.account.host=https://api.mojang.com/ -Dminecraft.api.services.host=https://api.minecraftservices.com/ -Dminecraft.api.session.host=https://api.minehut.com/mitm/proxy
you are referring to this correct?
yeah I had to have mcprohosting do it themselves because its on thier backend for my hosting
yep, did that
is online mode set to true in server.properties?
no it wasnt
set it to true
ok,. i did and restarting now to test
had to restart again sorry, had conflicts with a plugin I had
so on the direct server join it says "failed to verify username" and on minehut same thing
I think I may know how to fix that
thats normal for direct. once you setup minehut flags, you can only join through minehut
but the flags are already setup, and can you not join normally throught a domain name at that point???
would a proxy server fix that issue?
with the minehut flags, you either have to join through minehut such as the lobby or the minehut ip. or a custom domain that goes through the minehut ip
gotcha
ya you can use a proxy to allow both minehut and external connections. you are gonna need 2 proxies tho. 1 proxy with the minehut flags. and the second proxy with normal settings
the failed to verify username one?
now it doesnt even show the server through direct server address connections but I think thats how it is supposed to work
but the minehut shows this still
so its not showing that failed to verify username one?
showing that for the minehut domain?
what would the minehut domain be?
one of the settings isn't setup correctly
which I think is correct becuase my server is only using 0.2GB of ram
in your server's console, can you take an image of the full startup flag being ran
you aren't using velocity. you dont need that enabled
these are the only errors im seeing on startup
so just change velocity to false then? any others?
yes set velocity to false
ok we now down to just this on startup
prevent-proxy-connections=false would that cause a issue? im assuming yes?
it should be false