ID:1668567
 
Resolved
Some routers confused the connection handshake process.
BYOND Version:507
Operating System:Windows 8 Pro 64-bit
Web Browser:Chrome 37.0.2062.102
Applies to:Webclient
Status: Resolved (507.1250)

This issue has been resolved.
Descriptive Problem Summary:
I'm currently hosting a bare bones chat room here.

When I join my own server through the link given to me in Dream Daemon, the interface is loaded properly, but the output contains the error code 9. However, when I replace my full IP with just "localhost" or "127.0.0.1", I can log in successfully.

When I log in successfully into any game that includes a map, Chrome's Task Manager tells me that the game's tab is taking 25 (max) CPU usage. I just tried a chat room and it's perfectly fine, sitting at 0-1 CPU.

Numbered Steps to Reproduce Problem:
1. Install BYOND 507.1248
2. Host anything in Dream Daemon
3. Join through given play link.
4. Receive error code 9.
5. Replace IP with localhost.
6. Log in successfully.

Yes, my ports are forwarded. Yes, I'm using the byond.com/play link.

Code Snippet (if applicable) to Reproduce Problem:
mob
verb/say(t as text) world << "<b>[key]</b>: [html_encode(t)]"
Login() world << "<i>[key] has logged in.</i>"
Logout() world << "<i>[key] has logged out.</i>"

// skin.dms
<style>
#input {
position: absolute;
bottom: 0;
width: 100%;
}
</style>
<body>
<div id=output byondclass=output></div>
<div id=input byondclass=input skinparams="command=say"></div>
</body>


Expected Results:
I can play games I host.

Actual Results:
No one can connect to games I host through the public link.
I can join using the local link, but having a map causes max CPU usage in the tab.

Does the problem occur:
Every time? Or how often? Every time
In other games? Yes
In other user accounts? The pre-game ad displays perfectly! But yes, the problem persists. Other people haven't been able to join either.
On other computers? Yes (my phone, too!)

edit: so far, one person has been able to join the link!
Descriptive Problem Summary:
I'm hosting Treasure Quest at http://www.byond.com/play/71.29.148.3:56667 but when I log in with the webclient, I get an empty box. Tried a few other games as well. I can log in fine with DS, and DD reports that my port can be reached, but no joy...
Numbered Steps to Reproduce Problem:

Code Snippet (if applicable) to Reproduce Problem:


Expected Results:

Actual Results:

Does the problem occur:
Every time? Or how often?
In other games?
In other user accounts?
On other computers?

When does the problem NOT occur?

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)

Workarounds:

In response to Flick
I am in! Although the initial connection ("downloading client" -- did it get there for you?) took a lot longer than it should have, so that's something we'll want to look at.

My best guess is that you have a loopback on your router that isn't letting you connect out to your public ip. Can you login to that ip:port combo directly from DS, or do you have to use localhost. Have you tried http://www.byond.com/play/127.0.0.1:56667?
In response to Flick
I've also experiencing the same problem:

BYOND Version: 507.1248
OS: Windows XP Pro SP3
Web Browser: Chrome 36.0.1985.143

Screenshot: http://i61.tinypic.com/r8hsu1.jpg
In response to Flick
Oh, it would seems that ip:port (127.0.0.1) works.
In response to Flick
I've noticed that the webclient doesn't play nice with the firefox noscript addon. You have to allow scripts on the byond website in noscript and then do some other stuff so that noscript doesn't block the application.
Can confirm: I hosted my own instance of the same project and got the same error when joining through the web link.
Is your web link a direct IP address, e.g. 1.2.3.4:5555, or is it a domain?

I can think of only certain scenarios where this kind of issue would occur, and some kind of mismatch between a domain and world.internet_address would probably do it.
In response to D4RK3 54B3R
D4RK3 54B3R wrote:
I've noticed that the webclient doesn't play nice with the firefox noscript addon. You have to allow scripts on the byond website in noscript and then do some other stuff so that noscript doesn't block the application.

Well yeah, that's a given since this engine runs in JavaScript. I should add <noscript> tags to the page to make that clearer, though. It'd also be nice if we had a way to detect that in the iframe, so I think the server also should spit out a <noscript> tag with instructions. That would be a big help to users who want to keep using noscript.
In response to Syxoul
Syxoul wrote:
I've also experiencing the same problem:

BYOND Version: 507.1248
OS: Windows XP Pro SP3
Web Browser: Chrome 36.0.1985.143

Screenshot: http://i61.tinypic.com/r8hsu1.jpg

As you're having an issue with your external IP, these are my followup questions:

- Can you join that address via DS? It could be something as simple as port forwarding not being setup.
- Is that an IP or a domain? The screenshot redacts it so I assume it's the former, but I'd like to be sure.
- Are you running noscript or anything that would cause scripts to behave differently?
In response to Lummox JR
I'm using my external IP address that all the computers in my LAN use. I don't think it's a domain. I should know if it's a domain, right?
Yeah, I meant if you just had a custom domain name pointing to the address or something. The address you used to connect, does that match world.internet_address?
Can you join byond://public-ip:port in DS?
Yes, it matches.
world.internet_address: 24.113.193.54
Play link: http://www.byond.com/play/24.113.193.54:6002

Yes, joining in DS is working as it always has.
I was able to join your link okay. Interestingly though, I discovered a problem in the database while I was checking this out, that needed correcting. I don't think it's likely to have interfered with your testing, but it's a possibility.
At the moment, the web client isn't getting past 0% in the loading screen. I'm using two different computers (in the same network) and getting the same result.

Still, replacing the pulic IP with "localhost" or "127.0.0.1" is letting me fully connect with the web client.
Interestingly I am seeing some interesting indications of your IP being a bit confused in the server. It looks like the server thinks you're connecting from the LAN instead of from your external IP, which matches what Tom mentioned about a loopback. I'll see if there's a way I can deal with that. Even if I can only check for a LAN address matching the world.address, that would likely fix your issue.
Lummox JR resolved issue with message:
Some routers confused the connection handshake process.
when i try to join my own server i get this error.
Connection broken by server (error code 9)
http://www.byond.com/play/93.95.149.218:49980
its currently on.
In response to Gojan
This should be fixed in the latest release.
Page: 1 2 3