Descriptive Problem Summary:
I am hosting my world DMB with Dream Daemon and I have enabled the web client functionality via the drop-down.
I am hosting my world in safe mode and publically, on a port that Dream Daemon reports can be reached by players.
When navigating to the given web client URL (http://www.byond.com/play/[myip]:[myport]), the world never loads.
Instead, a black screen with a loading icon is shown, with a red progress bar at the bottom. The bar appears completely full, and says "Connected to world, downloading client"
Numbered Steps to Reproduce Problem:
1. Hosted game in Dream Daemon on a publically accessible port and with webclient connections enabled
2. Navigate to the web client URL reported by DreamDaemon
Expected Results:
World should load.
Actual Results:
Client appears stuck
Does the problem occur:
Every time? Or how often?
Every time.
In other games?
Unknown
In other user accounts?
Unknown
On other computers?
Unknown
When does the problem NOT occur?
The embed link (http://www.byond.com/play/embed/[myip]:[myport]) does seem to work.
Did the problem NOT occur in any earlier versions? If so, what was the last version that worked?
Unknown
Workarounds:
Unknown
ID:2193575
![]() Dec 29 2016, 5:20 pm (Edited on Dec 29 2016, 5:27 pm)
|
|||||||||||||
| |||||||||||||
![]() Dec 29 2016, 8:06 pm
|
|
Can you post some javascript console output from the failures?
|
Curious. The game actually is loading, because you can see it in the output. If you can send me the source I can test it on my end to be sure.
|
This seems happens with any game I host.
I just tried again and there is some additional output in the console that was not there in earlier tests: webclient.dart.js:5504 Quit: code 9 webclient.dart.js:5504 Socket: close Here's a screenshot of the window: ![]() I am using: BYOND 5.0 Beta (Version 511.1377) on Linux |
Quit code 9 is an authentication failure.
Are you connecting to a domain or to an IP? And does the webclient work when the IP address is 127.0.0.1? |
I am using my public facing IP address and I've configured port forwarding. DreamDaemon says "The BYOND hub reports that port 2000 is reachable."
If I use 127.0.0.1, it does seem to work. |
I've also been incapable of using the web client lately, since that UI overhaul for the log in screen, resource downloads happen but they get stuck at the very end and that's everything.
![]() Just stays stuck like this forever. This is on Chrome 56.0.2924.87 on MacOS by the way. |
Actually, after disabling uBlock, I'm getting the exact same code 9 thing as Airjoe, damn.
|
PJB, Airjoe, is there any chance a proxy of some kind is in the way? The authentication should work fine with a public-facing IP.
|
Not sure how I would figure that out, other than running a traceroute:
$ traceroute game.ss13.moe |
The missing hops in the traceroute, especially at the beginning, make me wonder if something could be hiding there that might explain the difference.
I think what I should do is probably in the next release, add something to the failure info to describe the host's IP/domain as seen by the server. |
Yeah I just ran another traceroute, and most of the missing ones at the end were gone, still broken though.
|
I am still having this issue with 512.1407 as of:
Chromium Version 62.0.3202.94 (Official Build) Built on Ubuntu , running on LinuxMint 18 (64-bit) Google Chrome Version 63.0.3239.132 (Official Build) (64-bit) Using 127.0.0.1 in the URL works, but using either my own internal IP (e.g, 192.168.1.10) or my public-facing IP doesn't work. Again, DreamDaemon is showing the "The BYOND hub reports that port 5555 is reachable." message. |
A little more info:
When I access http://www.byond.com/play/embed/[my-public-ip]:5555, DreamDaemon outputs: BYOND Error: failed to certify (null) from ip 192.168.1.1, origin [my-public-ip]:5555 When I access http://www.byond.com/play/embed/192.168.1.10:5555, DreamDaemon outputs: BYOND Error: failed to certify (null) from ip 192.168.1.10, origin 192.168.1.10:5555 When I access http://www.byond.com/play/embed/127.0.0.1:5555, DreamDaemon does not output any "BYOND Error: failed to certify..." messages. |