# Roundcube CSS can't load when domain URLs are used

**URL:** <https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048>\
**Category:** General Interworx Control Panel Info\
**Created:** [August 28, 2026, 2:34am UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048 "2026-08-28T02:34:04Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![sysnop](https://forums.interworx.com/letter_avatar_proxy/v4/letter/s/cdc98d/32.png) [@sysnop](https://forums.interworx.com/u/sysnop)\
**Post date:** [August 28, 2026, 2:34am UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/1 "2026-08-28T02:34:04Z")

</div>

Something prevents Roundcube CSS from loading only when a domain is part of the webmail URL. Layout displays properly as long as server IP or hostname over port 2443 are used, or when accessed from Siteworx.

The domain glitch occurs in any browser. Firefox console shows errors such as _stylesheets fetch failed_ and _Error while parsing stylesheet_ along with _NS\_ERROR\_NET\_PARTIAL\_TRANSFER_ for CSS and font assets.

Where should I be looking to find and fix the problem?

---

<div class="post-metadata">

**Author:** ![IWorx-Jenna](https://forums.interworx.com/user_avatar/forums.interworx.com/iworx-jenna/32/41_2.png) [@IWorx-Jenna](https://forums.interworx.com/u/IWorx-Jenna)\
**Post date:** [August 28, 2026, 2:07pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/2 "2026-08-28T14:07:47Z")

</div>

Hello–

This is a known issue. I do not have an ETA as to when the fix will be released. Please use 2443 in the url for the time being. We have to release a new version of httpd-iworx to resolve the issue.

Note, you should be able to use the domain in the url, it just has to be [domain.com:2443/roundcube](http://domain.com:2443/roundcube) or /webmail. Though that connection will show as insecure since the SSL cert that covers 2443 is for the hostname, not the domain.

Thanks,  
-Jenna

---

<div class="post-metadata">

**Author:** ![tudornet](https://forums.interworx.com/letter_avatar_proxy/v4/letter/t/82dd89/32.png) [@tudornet](https://forums.interworx.com/u/tudornet)\
**Post date:** [August 28, 2026, 2:28pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/3 "2026-08-28T14:28:30Z")

</div>

We had this and fixed it. Will go back and look for the fix, had to override something to do with the cache within the httpd.conf for iWork back end.

---

<div class="post-metadata">

**Author:** ![IWorx-Jenna](https://forums.interworx.com/user_avatar/forums.interworx.com/iworx-jenna/32/41_2.png) [@IWorx-Jenna](https://forums.interworx.com/u/IWorx-Jenna)\
**Post date:** [August 28, 2026, 3:39pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/4 "2026-08-28T15:39:56Z")

</div>

Hello–

Please do not make changes to the internal httpd.conf file. Doing so may cause unexpected issues down the line.

Thanks  
-Jenna

---

<div class="post-metadata">

**Author:** ![sysnop](https://forums.interworx.com/letter_avatar_proxy/v4/letter/s/cdc98d/32.png) [@sysnop](https://forums.interworx.com/u/sysnop)\
**Post date:** [August 28, 2026, 6:24pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/5 "2026-08-28T18:24:15Z")

</div>

> [@IWorx-Jenna](#):
>
> This is a known issue.

Thanks, good to know.

> [@IWorx-Jenna](#):
>
> Please do not make changes to the internal httpd.conf file.

If you mean the iworx instance, in particular proxy stuff, that’s sacred ground I would never mess with.

---

<div class="post-metadata">

**Author:** ![tudornet](https://forums.interworx.com/letter_avatar_proxy/v4/letter/t/82dd89/32.png) [@tudornet](https://forums.interworx.com/u/tudornet)\
**Post date:** [August 28, 2026, 6:44pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/6 "2026-08-28T18:44:43Z")

</div>

/home/interworx/etc/httpd/httpd-last.conf

**Commented out:**

# AddOutputFilterByType DEFLATE text/html

# AddOutputFilterByType DEFLATE text/css

Added after closing for

\<LocationMatch “^/roundcube/static.php/”\>  
RemoveOutputFilter DEFLATE

This isnt a 100% fix but workaround that works that we are using until patched.

---

<div class="post-metadata">

**Author:** ![IWorx-Jenna](https://forums.interworx.com/user_avatar/forums.interworx.com/iworx-jenna/32/41_2.png) [@IWorx-Jenna](https://forums.interworx.com/u/IWorx-Jenna)\
**Post date:** [August 28, 2026, 7:07pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/7 "2026-08-28T19:07:57Z")

</div>

Hello–

I mean _any file_ under the /home/interworx/etc/httpd/ directory.

Changes made to those files may cause unforeseen issues down the line. Especially since we do not overwrite those files upon update, if they have been edited.

So if we made an update to httpd-iworx that includes required changes to /home/interworx/etc/httpd/httpd-last.conf, since you edited that file, you will never get that part of the update. It will be added to httpd-last.conf.new, instead. And, since the new version of httpd-iworx can’t see the required changes to the conf file, your GUI may break.

For this reason (on top of others, such as just a typo potentially breaking something), we ask that customers never edit those files, themselves. I’ve seen so many servers where edits made to those files just broke everything in ways that took me hours to fix.

Thanks,  
-Jenna

---

<div class="post-metadata">

**Author:** ![sysnop](https://forums.interworx.com/letter_avatar_proxy/v4/letter/s/cdc98d/32.png) [@sysnop](https://forums.interworx.com/u/sysnop)\
**Post date:** [August 28, 2026, 8:16pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/8 "2026-08-28T20:16:01Z")

</div>

I appreciate the hack and even if I don’t use it I learned something from it. static.php came up a lot during my research, apparently it’s been controversial. Thanks for taking the time.

---

<div class="post-metadata">

**Author:** ![IWorx-Jenna](https://forums.interworx.com/user_avatar/forums.interworx.com/iworx-jenna/32/41_2.png) [@IWorx-Jenna](https://forums.interworx.com/u/IWorx-Jenna)\
**Post date:** [August 31, 2026, 6:58pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/9 "2026-08-31T18:58:04Z")

</div>

Hello–

We just released the fix for this issue. It is an update to httpd-iworx. The fixed version is httpd-iworx-2.4.68-15

Your servers should automatically update the next time the daily cron runs. Alternately, you can update manually with

```auto
yum clean all
yum update *.iworx.*

```

Thanks,  
-Jenna

---

<div class="post-metadata">

**Author:** ![sysnop](https://forums.interworx.com/letter_avatar_proxy/v4/letter/s/cdc98d/32.png) [@sysnop](https://forums.interworx.com/u/sysnop)\
**Post date:** [August 31, 2026, 11:02pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/10 "2026-08-31T23:02:19Z")

</div>

That was quick, thanks! Update fixed it.

---

<div class="post-metadata">

**Author:** ![vmk](https://forums.interworx.com/letter_avatar_proxy/v4/letter/v/919ad9/32.png) [@vmk](https://forums.interworx.com/u/vmk)\
**Post date:** [September 3, 2026, 6:15pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/11 "2026-09-03T18:15:08Z")

</div>

Seems like i got this problem still active (after all updates).  
If client using /webmail and replying email then got red message below: Connection Error (Failed to reach the server)!

If hostname over port 2443 are used everything works.

---

<div class="post-metadata">

**Author:** ![IWorx-Jenna](https://forums.interworx.com/user_avatar/forums.interworx.com/iworx-jenna/32/41_2.png) [@IWorx-Jenna](https://forums.interworx.com/u/IWorx-Jenna)\
**Post date:** [September 3, 2026, 7:09pm UTC](https://forums.interworx.com/t/roundcube-css-cant-load-when-domain-urls-are-used/24048/12 "2026-09-03T19:09:42Z")

</div>

Hello–

That is a completely different issue. In the issue reported here, the CSS just looked weird–the inbox was just a plaintext list, the Roundcube icon took up the entire page, etc. There were not any errors, connection or otherwise. It was an issue with how the page looked–purely cosmetic. It had nothing to do with sending, replying, or receiving messages.

What you are reporting also has not been reported by anyone else, nor can it be reproduced on a test server.

Please submit a ticket to [support.interworx.com](http://support.interworx.com). Make sure to provide the IP or hostname of the server, steps to reproduce (credentials to an affected account can be left in a file on disk), and make sure that remote assistance is enabled: [How To: Enable Remote Assistance — InterWorx documentation](https://appendix.interworx.com/current/nodeworx/general/support/how-to-enable-remote-assistance.html)

Thanks,  
-Jenna
