3

Problem

I cannot access JetBrains YouTrack using Chrome or Internet Explorer, but I can access it using Firefox.

Background and troubleshooting that has already been performed

  • It is running on an Amazon EC2 instance.
  • I have hosted it on port 82.
  • I have TeamCity hosted on port 81 and that is working perfectly in any browser, from anywhere
  • I have opened up those ports in the Windows Firewall, as well as in the EC2 security group manager.
  • The same problem occurs whether I access the site:
    • using the public IP address from my laptop
    • using the public IP address while logged into the EC2 instance
    • using localhost on the EC2 instance.
  • The problem does not occur, i.e. everything works fine, if I try either of the three steps above using Firefox.
  • I'm pretty sure it was working in Chrome, but now I'm doubting myself.
  • Probably irrelevant: I recently had to stop and start the EC2 instance due to an underlying hardware error, so that it could be migrated to new infrastructure.
  • I've checked the network settings in IE and Firefox on my local machine, and they're both set up with default settings.

Question

What's with that?

Improve this question
4
  • AFAIK IE/Chrome will try to automatically configure proxy settings in a way that might not be the same as FF (the former will use Windows' network stack more than FF will). In the past I've found Fiddler to be a good tool for discovering "surprise" proxy settings. Tools => Fiddler Options => Gateway => Show Current Gateway Info.
    – ta.speot.is
    Dec 13, 2013 at 5:55
  • I did that. The output was: WPAD: Not detected
    – David
    Dec 13, 2013 at 5:58
  • 1
    While Fiddler is running can you try accessing it with FF/IE and watching what happens? Also in IE are you trying http://whatever:82 i.e. including the protocol (https if necessary). From past experience IE doesn't try to guess protocols if you give it a non-standard port.
    – ta.speot.is
    Dec 13, 2013 at 5:59
  • Thanks, ta.speot.is. Using fiddler to look at the request made the problem apparent.
    – David
    Dec 13, 2013 at 6:08

1 Answer 1

Reset to default
1

There's a configuration problem that is redirecting to /login with a malformed ip address, so the 302 redirect request was failing.

I must have just been logged in on firefox, so no redirection was taking place.

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .