Question

We have fogbugz+kiln running on a server, and access is working great in our internal network.

We want to enable remote users to access fogbugz through our firewall, to accomplish this we have opened a port on our firewall, and have the firewall re-directing traffic to the fogbugz server.

our setup :-

internal url : http://mybugz external url : http://www.mycompany.com:48080

while this works fine, some things are failing due to fogbugz removing the :48080 part of the url seemingly at random.

for example, sometimes when adding a case it will redirect to http://www.mycompany.com/default?xxx which of course returns a 404 error.

also, the kiln link doesnt work, it ignores the :48080 part of the url entirely.. (but works if we go directly to http://www.mycompany.com:48080/kiln )

Is there some setting that we're missing, or is this a bug?

We have set the site configuration url to the :48080 url, but it still happens.

Case FC1928857

Answer 1

Update: The issue was found to be a problem with the Kiln Storage Service and a webserver which does not listen on port 80. The bug has been fixed for an upcoming release of Kiln.

---

I'm currently working with another customer on the same issue as you're having. I will update here when I have the solution (hopefully very soon!)

In the meantime, can you try setting sRedirectBase?

http://fogbugz.stackexchange.com/questions/3122/my-fogbugz-install-is-behind-a-load-balancer-and-it-appears-that-pages-are-being