Stops at "Connected! Loading website..." when I try to login

Woopra Forums » Troubleshooting » Bug Reports

Stops at "Connected! Loading website..." when I try to login

(69 posts)

Started 5 months ago by raakanin
Latest reply from bookboy
This topic is not a support question

Tags:

« Previous 1 2 3 Next »

simonbugler
Member

Yes The Handyguys looks to be correct - it works perfectly at home but not at work - I have requested our IT look into it...

Posted 5 months ago #
Jordan
Member

I'm having the same problem too, can login at home without a hitch, but at work it hangs. I've asked my IT department about it

Posted 5 months ago #
BunnDev
Member

Yep, just let us know what we need to unblock on the firewall.

Posted 5 months ago #
BunnDev
Member

Any news on this?

Posted 5 months ago #
BunnDev
Member

Hi, to answer my own question if you unblock MSNP (port 1863) on your firewall the software connects. Unfortunately I think this is a port that Microsoft Messenger uses so may not be a port corporate users would be happy to unblock.

Posted 5 months ago #
Elie El Khoury
Member

@BunnDev:

That's right, Woopra uses the port 1863. We will change this port on the next release.

Posted 5 months ago #
BunnDev
Member

Okay, thanks. Make sure you tell us which it is! ;-)

Posted 5 months ago #
Elie El Khoury
Member

Probably: 10452 :)

Posted 5 months ago #
James
Member

Any idea when this might happen? It seems a small thing to change the port and issue and updated version.

Posted 5 months ago #
The Handyguys
Member

One observation - My woopra client, according to Comodo Firewall Pro, is listening on TCP port 10453. This is a personal firewall.

To the Woopra team. I would imagine most people having these issues are monitoring blogs they maintain outside of their normal day job. Asking a corp IT security person to open any firewall ports for something like woopra would likely be a no no. I would suggest woopra try to do what they need to do over port 80 if possible or make it work via some type of external proxy/port forwarder that will allow woopra to work on its port and allow people behind corp firewalls to use port 80. To those that are curious, port 80 is a standard web port and is open virtually everywhere.

Posted 5 months ago #
Elie K
King of blues

Port 80 is used for HTTP Requests, but Woopra's protocol runs over an open socket which cannot run on port 80. Some ISPs will force the HTTP protocol on port 80.

About the 10453, it has nothing to do with your connectivity, it's a local server socket used for local feature.

Chief Eye Candy Officer

Posted 5 months ago #
ellaella
Member

I've had this problem for about 40 hours now, after everything had been fine. Is this any guesstimate when it might be resolved?

Posted 4 months ago #
Bauer Big City Network
Member

Hey,

Just had my a meeting with our IT guy - when will the port used change from 1863?

Mark.

Posted 4 months ago #
Bauer Big City Network
Member

Just had an email from our IT guy - apparently there is something on my machine which is upsetting the network firewall:

Event Type: Error
Event Source: Microsoft Firewall
Event Category: None
Event ID: 21285
Date: 20/05/2008
Time: 11:03:18
User: N/A
Computer: MANISA01

Description:
The number of HTTP requests per minute from the source IP address {local ip} exceeded the configured limit. ISA Server will block new HTTP requests sent from this IP address. This event indicates that this IP address probably belongs to an infected host. See the product documentation for more information about ISA Server flood resiliency.

This seems to be when Woopra was stuck at 'Connected! Loading Websites.' - Any ideas guys?

Posted 4 months ago #
Bauer Big City Network
Member

Can I aire a slight concern on this topic - we haven't had a response from an official member of the development team in a number of days now, and as this is a major issue which would affect the viability of this platform for our network of radio station websites at least, we need to know that this issue is being looked into and when the fix is to be expected.

Apologies for making such a public statement of concern, however I doubt we are the only potential user of this system awaiting a response from your team on this.

Kind Regards,
Mark Newby,
Group Developer,
Bauer Radio (Big City Network)

Posted 4 months ago #
James
Member

Seconded.

Can we get some sort of response on this? At the very least an acknowledgment that you are aware of the issue, with hopefully an idea of a proposed solution and implementation date.

James

Posted 4 months ago #
Bauer Big City Network
Member

As there still hasn't been a reply on this I'm afraid we've had to uninstall the tag from our website. Our network has a high UU and PV count and we therefore cannot wait around a week for a response from developers on an issue as commercially important to us as this.

We are more than interested in supporting new technology and new web developments, however this is only true when the development team are in close (near daily at worst) contact.

I wish you well wish this project.

Mark Newby,
Group Developer
Bauer Radio.

Posted 4 months ago #
Greg
Member

Wish we could get some good news about this ... sooner than later.... WTF?

Posted 4 months ago #
Motorcycle Insight
Member

Why not connect via port 443? It's almost universally left open due to SSL using it.

It's also disconcerting to see this issue not be addressed yet.

Posted 4 months ago #
Greg
Member

I've updated to the latest beta 1.1.2.2 (new as of this morning, it seems) ... still no joy.

I've tried opening the various ports you mention and arranging proper NAT traversal ... however I'm not even seeing any attempts on these ports for the firewall.

It should be noted that Woopra USED to work for me and I've changed nothing except for the update to the various woopra versions ... I didn't have to do anything to the firewall to get it working originally.

At this point it is officially taking up too much of my time trying to get Woopra folks to resolve this. I'm officially signing off for a few weeks. Hopefully when I come back it'll be fixed, but at this point I can't test jack if I can't log in.

Thanks

g

Posted 4 months ago #
James
Member

Just bumping this topic to the updated topics page as it is still an unresolved issue and in the hope that it might one day be picked up by the woopra techies for response or clarification.

Posted 3 months ago #
blueknight
Member

OK... after reading this post I took a look at the Firewall Logs and figured out exactly what needs to be opened on the firewall.

Outbound Connection from your PC only.

Your PC --> IP Address: 72.233.24.10 === TCP PORT: 1863

Hope this helps!

Posted 3 months ago #
James
Member

@blueknight: Thanks for the reply.

It has been sugested before that we open port 1863. Unfortunately on corporate networks with many clients this is often impossible.

I am looking for confirmation from the Woopra techies that they are indeed planning to change the Port to something less contraversial and some idea of where this might be in the Woopra roadmap.

It is not that I am demanding a solution right now (although that would be nice) - just some communication from Woopra would be enough!

Posted 3 months ago #
James
Member

Bumped.

Posted 3 months ago #
bookboy
Member

I'm in the same boat. Running 1.1.2.2 on my mac. This is the only version I have ever run. It used to work, then stopped last week. I had not changed anything. I've tried opening port 1863 to no avail.

Posted 3 months ago #
MacGeeky
Member

It was fine for a while, but today the problem came back. When I now try to login with the Woopra-client it stops at "Connected! Loading websites..." and after a while it just says "You have been disconnected".

Doesn't the woopra developers and the moderators of this forum care about what the users says? No one have answered this question for 2 months now, and that's just sad.

Fix this problem, or at least tell us why it happens, and what we can do to stop it from happening..

By the way, it's the same on both Windows and Mac, I've tried both!

Posted 3 months ago #
abdnuni
Member

Yes, we too are unable to connect - been trying all morning to no avail.

The problem's been there since yesterday mid-afternoon GMT+0.

It was connected. Next time I looked up it was not; and hasn't been able to connect since. Tried from two separate computers. ( It's through a corporate proxy )

Posted 3 months ago #
James
Member

Bumped again.

Lorrelle, can you shed any light on whether this is a port/NAT issue and if/when it will be resolved for those behind corporate networks?

Posted 3 months ago #
James
Member

Can we get an idea of when the proposed change of port from 1863 to 10452 is going to take place?

It was suggested by Elie that this would be in the next release however the new release candidate still seems to be stuck behind our corporate firewall.

Posted 2 months ago #
Barry
Member

I have been trying to connect for a couple of weeks now and am still unable to. Its just stuck on Loading Websites. I'm not behind a firewall at home. Has anyone managed to fix this?

Posted 2 months ago #