ID:1280398
 
Resolved
I'm closing this report, since it applies to an older build and the issue with port selection should be resolved in newer versions, specifically 1194 and 1195.
BYOND Version:499.1190
Operating System:Windows 7 Home Premium 64-bit
Web Browser:Chrome 27.0.1453.94
Applies to:BYOND Pager
Status: Resolved

This issue has been resolved.
Descriptive Problem Summary:
When running the new pager with version 499.1185 the pager was perfectly capable of connecting to the BYOND Central/Hub thing(whatever it is referred to now). Once I updated the byond version, however, it no longer connected -- at all. I attempted rebooting my computer, making sure my internet was working fine, uninstalling and re-installing the program, deleting the cache files, deleting the byond files themselves and re-installing that way(after uninstalling), and even waiting with it logged in for a long period of time; none of which worked. I then proceeded to downgrade the pager to the aforementioned BYOND version and it was capable of connecting again. I am unsure if this is an isolated incident, or not, but I figured it would be a good idea to report it so that it doesn't start showing up for everyone later on.

Numbered Steps to Reproduce Problem:
1. Download & Install BYOND v499.1190
2. Sign into any BYOND account on the pager.
3. Wait for the small red bar giving the message referring to having no connection to BYOND.

Code Snippet (if applicable) to Reproduce Problem:


Expected Results:
Normal functionality for the pager, such as accessing game Hubs and paging friends, and playing games.

Actual Results:
Pager was not functioning: Could not message friends, could not visit hubs via the in-pager feature, could not view resources, all games connected to replied with "Connection Failed".

Does the problem occur:
Every time? Or how often? Every Time.
In other games? All games.
In other user accounts? Yes.
On other computers? Untested.

When does the problem NOT occur?
On any versions 499.1185 and prior(have not tested the versions between that and 499.1190).

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

Workarounds:
Are you certain this isn't due to a firewall flagging the new version? It would help if you could test every intermediate (in http://www.byond.com/download/build/499/) to see what works.
I ran it with my firewalls and anti-virus off just to check as well, forgot to mention that.
Ok, well try the other versions in between so we can see if there's a particular point where the issue came up.
Also, it seems to not work for those intermediate versions either. I just ran a test through them.
It really seems like a firewall issue here. Can you uinstall BYOND, redownload 1185, and retest it? I can't imagine there's anything different between 1185 and 1186 that would cause this problem.
Some random new issue just showed up, actually.

You can see it here:
http://oi41.tinypic.com/avpwm8.jpg
And I've set the BYOND program to be allowed by Microsoft Security Essentials(my anti-virus) and by my firewall.
Update: I tried the newest build that was just released, and the problem seems to persist still.


Here's an image: http://i40.tinypic.com/2s7xg93.png

Edit: This happens when I try to join a game: http://i41.tinypic.com/9hor53.png
Also, I seemingly can connect with Dream Daemon, not sure if that means anything or not.
I know it seems like I've been posting an awful lot recently, but I just connected as a guest and tried to connect to a game and..it connected.

http://i39.tinypic.com/jkk4rm.png

I tried connecting on other accounts besides the one I usually get on, and even borrowed one temporarily from a friend..but it repeats the issue I have on this account.
In response to Ernesto5432
Ernesto5432 wrote:
I know it seems like I've been posting an awful lot recently, but I just connected as a guest and tried to connect to a game and..it connected.

http://i39.tinypic.com/jkk4rm.png

I tried connecting on other accounts besides the one I usually get on, and even borrowed one temporarily from a friend..but it repeats the issue I have on this account.

Maybe its time to clean out the my documents/byond folder?
I deleted the folder and even tried installing it to a new location.
In response to Ernesto5432
Ernesto5432 wrote:
I deleted the folder and even tried installing it to a new location.

when you say "the folder", which folder, exactly? Byond stores a few things in a few different places.
The entire folder which BYOND was installed within, and my %Temp% folder for good measure.
In response to Ernesto5432
Ernesto5432 wrote:
The entire folder which BYOND was installed within, and my %Temp% folder for good measure.

Those folders, unfortunately, have nothing to do with what byond actually saves and caches. The cache is located in "My Documents/Byond"... There's a lot of stuff in there that you might not want to lose, so be sure to create a back up of it before you try removing it.
Yes, as in that folder. I installed it to C:\Users\...\Documents\BYOND.

All the \cache, \cfg, etc. have been deleted before reinstalling.
Question, does the new pager require ports to be open? If so, I have a secure NAT so that could cause issues.

Only thought about this while I was playing warframe due to issues loading my friends-list on it.
The new pager shouldn't have any restrictions over the old pager. Your computer needs to be able to connect to byond.com and hub.byond.com. Almost invariably when there are connection issues, it's due to Windows Firewall restricting the new application.
Alright, I got around to configuring my firewall to re-allow BYOND through, but regardless of what I do, even after disabling windows firewall, nothing changes. It remains like this: http://i44.tinypic.com/34spesn.png
Update: I just went scrounging around for the beta version I had been using prior to the update to 499.1885, which was 499.1184, and I found that it connects perfectly fine to the HUB and BYOND.com.

Hopefully this will shed some light on possible fixes or maybe what could have changed to make it not work on some people's machines.
Page: 1 2