Closed SarahGreyWolf closed 2 years ago
Your domain (space.domain.tech
) doesn't seem to exist, or at least I can't seem to resolve it.
However when entering this into direct connect it removes the path and just attempts to connect to space.domain.tech:1212 or space.domain.tech:443 if using ss14s.
That's because to send the HTTP request, it has to first connect a TCP socket to either space.domain.tech:1212
or space.domain.tech:443
. It can't even connect to your server in the first place, so the query path (which is part of HTTP, not TCP) isn't even mentioned in the error message.
Sorry, I gave domain as an example really, but if you need it for testing it would be space.sarahgreywolf.tech and space.sarahgreywolf.tech/play
Unsure what I did but it seems to be mysteriously working now, as is the way of software I guess, thanks anyway, and thanks for the great project
Hi I'm using a proxy to convert http to https aswell as allow for subdomains on the same server. I would like to be able to have it connect at space.domain.tech/play to perform the /info request. This would allow me to have space.domain.tech itself for information on the server and the current round. However when entering this into direct connect it removes the path and just attempts to connect to space.domain.tech:1212 or space.domain.tech:443 if using ss14s.
I have included the stack trace though it's just a generic "No such host is known" error.