Incorrect JavaScript chunk

Oct 13, 2025 by orovajewels.com 34 views

Introduction

In this article, we will explore a common issue that has been reported by Rocket.Chat users after upgrading to version 7.4. The livechat widget, which was previously working flawlessly, now attempts to connect to localhost instead of the correct API instance. We will delve into the possible causes of this issue, provide steps to reproduce, and offer solutions to resolve the problem.

Description

Recently, several users have reported that their livechat widget began attempting to connect to localhost after upgrading to Rocket.Chat version 7.4. The widget loads correctly, retrieves all JavaScript chunks, but then directs the browser to request the wrong URL, which is http://localhost:3000/api/v1/livechat/config. This issue is not related to the Apache configuration or Rocket.Chat settings, but rather a client-side problem.

Steps to Reproduce

To reproduce this issue, follow these steps:

Upgrade to Rocket.Chat version 7.4.1.
Load the livechat widget in your browser.
Observe that the widget loads correctly, but then attempts to connect to localhost.

Expected Behavior

Once the livechat widget loads, it should connect to the same API instance where the widget was loaded. In this case, the expected behavior is that the widget should connect to the correct URL, which is https://chat.example.com/api/v1/livechat/config.

Actual Behavior

The actual behavior is that the widget loads correctly, retrieves all JavaScript chunks, but then directs the browser to request the wrong URL, which is http://localhost:3000/api/v1/livechat/config.

Server Setup Information

Version of Rocket.Chat Server: 7.4.1
License Type: Community
Number of Users: 25
Operating System: Ubuntu 20.04.6
Deployment Method: Manual
Number of Running Instances: 1
NodeJS Version: v22.13.1
MongoDB Version: v7.0.17

Client Setup Information

Desktop App or Browser Version: Browser
Operating System: MacOS Firefox, Chrome, Safari

Additional Context

This is a manual install, and it has been working flawlessly for years. No changes to the Apache configuration or Rocket.Chat settings have recently occurred other than the upgrade to version 7.4.

Relevant Logs

If logs are useful in this case, we can provide them. However, as this appears to be a client-side issue, we are not sure if logs will be helpful.

Possible Causes

Based on the information provided, the possible causes of this issue are:

Incorrect JavaScript chunk: The JavaScript chunk responsible for the wrong connection to localhost may be the culprit.
Client-side issue: The issue may be related to the client-side configuration or settings.
Rocket.Chat version 7.4.1: The upgrade to version 7.4.1 may have introduced a bug or changed the behavior of the livechat widget.

Solutions

To resolve this issue, try the following solutions:

Check the JavaScript chunk: Verify that the JavaScript chunk responsible for the wrong connection to localhost is not the issue.
Check client-side configuration: Review the client-side configuration and settings to ensure that they are correct.
Downgrade to previous version: If the issue persists, try downgrading to the previous version of Rocket.Chat.
Contact Rocket.Chat support: If none of the above solutions work, contact Rocket.Chat support for further assistance.

Conclusion

In conclusion, the livechat widget trying to connect to localhost is a common issue that has been reported by Rocket.Chat users after upgrading to version 7.4. By following the steps to reproduce, understanding the expected and actual behavior, and trying the solutions provided, you should be able to resolve this issue and get your livechat widget working correctly again.

Apache Configuration

ServerName chat.example.com
ErrorLog /var/log/apache2/chat-error.log
CustomLog /var/log/apache2/chat-access.log combined
<Location />
    Require all granted
</Location>
RewriteEngine On
RewriteCond %{HTTP:CONNECTION} Upgrade [NC]
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*)           ws://localhost:3000/$1 [P,L]
RewriteCond %{HTTP:Upgrade} !=websocket [NC]
RewriteRule /(.*)           http://localhost:3000/$1 [P,L]
ProxyPassReverse /          http://localhost:3000/
SSLCertificateFile /etc/letsencrypt/live/chat.example.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/chat.example.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf

Livechat Widget Script

(function(w, d, s, u) {
    w.RocketChat = function(c) { w.RocketChat._.push(c) }; w.RocketChat._ = []; w.RocketChat.url = u;
    var h = d.getElementsByTagName(s)[0], j = d.createElement(s);
    j.async = true; j.src = 'https://chat.example.com/livechat/rocketchat-livechat.min.js?_=202503120000';
    h.parentNode.insertBefore(j, h);
})(window, document, 'script', 'https://chat.example.com/livechat')

Steps to Reproduce

Upgrade to Rocket.Chat version 7.4.1.
Load the livechat widget in your browser.
Observe that the widget loads correctly, but then attempts to connect to localhost.

Expected Behavior

Once the livechat widget loads, it should connect to the same API instance where the widget was loaded.

Actual Behavior

Introduction

In our previous article, we explored a common issue that has been reported by Rocket.Chat users after upgrading to version 7.4. The livechat widget, which was previously working flawlessly, now attempts to connect to localhost instead of the correct API instance. In this article, we will provide a Q&A guide to help you understand and resolve this issue.

Q: What is the livechat widget trying to connect to?

A: The livechat widget is trying to connect to localhost instead of the correct API instance.

Q: Why is this happening?

A: This issue is likely caused by a client-side problem, such as an incorrect JavaScript chunk or a misconfigured client-side setting.

Q: What are the possible causes of this issue?

A: The possible causes of this issue are:

Incorrect JavaScript chunk: The JavaScript chunk responsible for the wrong connection to localhost may be the culprit.
Client-side issue: The issue may be related to the client-side configuration or settings.
Rocket.Chat version 7.4.1: The upgrade to version 7.4.1 may have introduced a bug or changed the behavior of the livechat widget.

Q: How can I resolve this issue?

A: To resolve this issue, try the following solutions:

Check the JavaScript chunk: Verify that the JavaScript chunk responsible for the wrong connection to localhost is not the issue.
Check client-side configuration: Review the client-side configuration and settings to ensure that they are correct.
Downgrade to previous version: If the issue persists, try downgrading to the previous version of Rocket.Chat.
Contact Rocket.Chat support: If none of the above solutions work, contact Rocket.Chat support for further assistance.

Q: What are the steps to reproduce this issue?

A: To reproduce this issue, follow these steps:

Upgrade to Rocket.Chat version 7.4.1.
Load the livechat widget in your browser.
Observe that the widget loads correctly, but then attempts to connect to localhost.

Q: What is the expected behavior of the livechat widget?

A: The expected behavior of the livechat widget is that it should connect to the same API instance where the widget was loaded.

Q: What is the actual behavior of the livechat widget?

A: The actual behavior of the livechat widget is that it loads correctly, retrieves all JavaScript chunks, but then directs the browser to request the wrong URL, which is http://localhost:3000/api/v1/livechat/config.

Q: Can I provide logs to help diagnose this issue?

A: Yes, if logs are useful in this case, we can provide them. However, as this appears to be a client-side issue, we are not sure if logs will be helpful.

Q: What is the Apache configuration for this issue?

A: The Apache configuration for this issue is:

ServerName chat.example.com
ErrorLog /var/log/apache2/chat-error.log
CustomLog /var/log/apache2/chat-access.log combined
<Location />
    Require all granted
</Location>
RewriteEngine On
RewriteCond %{HTTP:CONNECTION} Upgrade [NC]
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*)           ws://localhost:3000/$1 [P,L]
RewriteCond %{HTTP:Upgrade} !=websocket [NC]
RewriteRule /(.*)           http://localhost:3000/$1 [P,L]
ProxyPassReverse /          http://localhost:3000/
SSLCertificateFile /etc/letsencrypt/live/chat.example.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/chat.example.com/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf

Q: What is the livechat widget script for this issue?

A: The livechat widget script for this issue is:

(function(w, d, s, u) {
    w.RocketChat = function(c) { w.RocketChat._.push(c) }; w.RocketChat._ = []; w.RocketChat.url = u;
    var h = d.getElementsByTagName(s)[0], j = d.createElement(s);
    j.async = true; j.src = 'https://chat.example.com/livechat/rocketchat-livechat.min.js?_=202503120000';
    h.parentNode.insertBefore(j, h);
})(window, document, 'script', 'https://chat.example.com/livechat')