A forum for technical support discussion related to Fogbugz.
Fogbugz is picking up the internal IP of our server (behind ISA) and putting that in the URL of the notification email 'link to your bug'.
I've checked in the server registry : HLM/Fog Creek/Fogbugz/C:zzzzz/sURL and that's correct.
Is this something I can fix?
Friday, March 4, 2005
What URL do you put into the browser when you create/edit the bug?
Traditionally (i.e. it was like this in 3.0), that's been the one which FB uses to make the links in outgoing emails.
You'll need to connect to it with the 'external' URL, even if you're internal. This can sometimes involve playing with NAT/router config, or adding an entry to your hosts file.
I don't acutally think this was a very good aspect of FB, so maybe it's been fixed in 4.
Friday, March 4, 2005
FogBugz asks the web server what its url is when you submit cases. The web server apparently decides by looking at the URL you used to access the server (so virtual hosts are correct). We rely on the webserver, which relies on the address you use.
Basically if you want to use the IP address to access, but you want the DNS name to be used in emails, you need to modify GetURLPrefix in util.asp.
I saw the RegEdit suggestion in a beta forum post somewhere - I put in the support.company.com URL in site admin and in the browser.
It's probably our ISA server messing around with the thing, but Michael - to pick your large brain - where does FB get that part of the URL from? Not from the site admin URL setting?
Monday, March 7, 2005
The URL in site admins is just for the maintenance service so it can find your FogBugz install.
For all email notifications, FogBugz gets its own URL by asking the web server what the current URL is. That is determined by how you access the fogbugz server.
So if I assign you a case when I have http://192.168.0.1/fogbugz in the address bar, the link you will get will be
For some reason however email's drop the port number when responding. This means the link is bad. Url is correct and putting the port number sends it straight there. Any idea why the port would get dropped?
Tuesday, March 22, 2005
This topic is archived. No further replies will be accepted.Other recent topics