RT 6.0.1 pages not updating after doing something

RT Users
1

Hello,

Why do pages no longer automatically update after executing an action? For example, if I search for something, a page with the search results does not load. Instead, a white overlay appears (see below).

Screenshot 2025-10-08 162822
Screenshot 2025-10-08 1628222532×1130 93.4 KB

This happens in other places too. For example, in query builder you have to manually navigate to the results page using “Show Results“ in the toolbar that appears.

Screenshot 2025-10-08 163415

And if you update a ticket, it doesn’t automatically reload and display the changes that have been made.

Is there something wrong with my RT 6 installation or this how it generally is?

2

This seems like an issue with HTMX re-loading parts of the page, if you’re not seeing a spinner I’d say it points to something being off with your RT.

I’d suggest starting by clearing your browser cache/private browser to see if its a caching issue

3

Clearing the browser cache didn’t help I’m afraid.

4

What do you see in the web inspector network and JS console tabs when this occurs? Any errors? What about the RT logs any errors there?

5

Thanks for the suggestion to check the JS console tab. This is what the console tab shows when the problem occurs:

SecurityError: Failed to execute ‘pushState’ on ‘History’: A history state object with URL ‘``http://REDACTED/Search/Results.html?Query=(%20Subject%20LIKE%20’star’%20OR%20Description%20LIKE%20’star’%20)%20AND%20(%20Status%20%3D%20’__Active__'%20)&q=star’`` cannot be created in a document with origin ‘``https://``REDACTED``’ and URL ‘``https://``REDACTED``/Search/Simple.html’``.
at $t (squished-5d619aff4f5704bed76bd5bdc698953b.js:1:28935)
at e (squished-5d619aff4f5704bed76bd5bdc698953b.js:1:47311)
at Dn (squished-5d619aff4f5704bed76bd5bdc698953b.js:1:48216)
at XMLHttpRequest. (squished-5d619aff4f5704bed76bd5bdc698953b.js:1:43356)

And RT is complaining about this in the logs:

[warning]: The requested port (80) does NOT match the configured WebPort (443). Perhaps you should Set($WebPort, 80); in RT_SiteConfig.pm, otherwise your internal hyperlinks may be broken. (/opt/request-tracker-6/sbin/../lib/RT/Interface/Web.pm:1690)

Is it an http to https redirect problem? I don’t have any redirects configured on the web server hosting RT.

6

Are you accessing RT over HTTP when you have it configured for HTTPS?

7

No. I’m accessing it only via HTTPS.

8

It got fixed. I added “SSLOptions +StdEnvVars“ to the Location section of the Apache virtual host configuration and now it’s working as it should.

Thanks for the help everyone.

1 Like