It depends on BYOND's policy. It's possible to prevent this issue, but do you want to go the extra mile?
| |
Tom wrote:
Can one of you try http://www.byond.com/download/build/507/507.1250_byond.zip to confirm that fixes the problem? It still doesn't work for me. Error code 9. The world.address and world.internet_address values are correct. When I connect using localhost, my client.address is 127.0.0.1, but when I connect (through DS as that's the only other way that works) through byond://external_ip:port my client.address is 192.168.1.1, even though my world.address is 192.168.1.135. Is that a problem? | |
DarkCampainger wrote:
Still not working for me, I'm still getting the "Connection broken by server (error code 9)" unless I swap the external address with localhost. If I open the BYOND client and use Open Location to connect to the external address, it works fine. Also, I do have port-forwarding set up. According to the hub it thinks you're on 192.168.1.1. Is that the same subnet as your world.address? | |
192.168.1.1 is the address I go to to log into the router. It's not any connected computer's address.
| |
Yes, my world.address is 192.168.1.100 and my router is 192.168.1.1.
However, I just tried it again and it started working. I can't explain why, all I did was add an output for world.address and internet_address, recompile, and rehost. I'm positive I recompiled in the new version several times before, but this time the webclient is working with my external address! Did you do some magic on the back end? | |
No, it appears there's a timing issue and that world.address wasn't filled in properly. Please test the new build to be sure this is fixed.
| |
Sir Lazarus wrote:
It depends on BYOND's policy. It's possible to prevent this issue, but do you want to go the extra mile? Here's the thing: Your network is configured so people inside it can't connect to it via the WAN address, only by another address you have internally. That isn't a common setup and isn't really something we could easily puzzle out (if it could be done at all). | |
Interesting. It looks like adding an override to world/New() to output the address is what made the previous build work for me. I can add/remove that code and it works/doesn't work reliably.
In the build Tom just posted, it seems to always work. So the fix looks good :) | |
I'm not so concerned about client.address being different; that's just what your router is choosing to do, and it makes sense to just go with it. Glad to know this issue is fixed for good this time. :)
| |
Lummox JR wrote:
Sir Lazarus wrote: It used to be pretty common older routers, which may still be in use today. Figuring it out is pretty easy: have DreamDaemon send a message to itself using the external IP address obtained from the hub. If it works, don't do anything. If it doesn't you can notify the hub that it should silently replace the external IP with the internal IP if the (web)client IP is the external one. | |
Getting error code 9 issues using webclient, as well. 508.1299.
Using webclient, I can do http://byond.com/play/embed/ anthroesoterica.servegame.com:10667 on any machine and it connects fine. http://127.0.0.1:10667/play on hosting server does not work. I get BYOND's loading screen and after 100% loading it fails. http://192.168.0.100:10667/play/ to access it from another system results in the same as above. This happens across Chrome and IE8+ DS connects fine from hub and direct input via the "Open" button, on any machine. Firewalls don't exist in this household. The server is DMZ on the network. Quite sure it's not a network problem on my end as all of my other servers on the same machine are perfectly functional. | |
Khyberkitsune wrote:
Getting error code 9 issues using webclient, as well. 508.1299. Clients should never use http://host:port/play the code 9 here is shown because you're not sending the authentication data, like the byond.com embedded/hosted version would. | |
ErikHanson wrote:
Khyberkitsune wrote: Works fine if you are or aren't logged in.. Auth data from BYOND.com shouldn't matter, guests are allowed to login, unless you turned that off.. | |
Khyberkitsune wrote:
Getting error code 9 issues using webclient, as well. 508.1299. Watch Chromes console when connecting, it has a huge issue with "insecure" ports... I reported this, not sure if it got stickied or not, nothing Lummox can do about it either. It's up to the host to choose a port number that'll work on all browsers, 80,8080 work fine. | |
ErikHanson wrote:
Khyberkitsune wrote: Logs show exactly the opposite of what you say. | |
I suspect the use of a domain is involved. This kind of issue has been hard to diagnose.
| |
Is there any information we could give you to help track this down?