Telegram Linking Error - Integration Service Not Available #7997

Title: Telegram Linking Error - Integration Service Not Available

Product: Huly

Component: Integration - Telegram

Version: (Unidentified)

Environment:
Browser: Chrome, Edge and Brave
Operating System: Windows 11 Pro
URL's: https://huly.app/workbench//setting and https://telegram.huly.app/signin
User: Account "Huly" (jasp402 - jasp402@gmail.com).

Description of the Defect:

The user is unable to link their Telegram account to the Huly platform through the Integrations section in the user settings. When attempting to link, the system remains in a "Connecting..." state indefinitely, without completing the process. Additionally, when accessing the Telegram integration service directly (https://telegram.huly.app/signin), a 502 Bad Gateway error is displayed, suggesting a problem on the server that manages the integration.

Steps to Replicate:

1. Log in to the "Huly" user account on the Huly platform.
2. Navigate to the "Settings" section of the user. (URL: https://huly.app/workbench//setting).
3. Select the "Integration" option.
4. In the Telegram section, click the "Add" button to start the linking process.
5. Enter a valid and working phone number in the corresponding field.
6. Click the "Next" button.

⚠️Notice that the "Next" button changes to "Connecting...", but the linking process does not complete, even after a long wait time (greater than 10 minutes).

Current Result:

Following the steps provided, you can see that:

When you click "Next", the button changes to "Connecting..." and remains in this state indefinitely.
There is no redirection or request for a verification code.
The Telegram integration is not activated.
The following error is logged in the browser console:

<!-- end list -->

Connect.svelte:64
POST https://telegram.huly.app/signin net::ERR_FAILED
26970.9015380….js:12

Uncaught (in promise) TypeError: Failed to fetch
at B (Connect.svelte:64:28)
at v (Connect.svelte:36:23)
at HTMLButtonElement.w (Connect.svelte:123:12)
at HTMLButtonElement.so (bundle.2ffc7d3c17743…0ce5.js:9863:129665)
When accessing https://telegram.huly.app/signin directly, an HTTP 502 Bad Gateway error is displayed, indicating a problem on the server.
Error Analysis (Potential Root Cause):

The "502 Bad Gateway" error when accessing https://telegram.huly.app/signin directly, along with the "net::ERR_FAILED" and "Failed to fetch" errors in the browser console when trying to link from Huly, clearly indicate a problem on the server side responsible for the Telegram integration.

It is highly likely that:*

The "telegram.huly.app" service is down, down, or experiencing serious errors. The 502 Bad Gateway error is a direct indicator that the Nginx server managing this service is unable to communicate with the backend server (application) that should process Telegram linking requests.
There could be a network or infrastructure issue preventing communication between the Nginx server and the Telegram integration service backend.
Although less likely, there could be a problem in the configuration of the Nginx that manages the "telegram.huly.app" service, preventing requests from being correctly directed to the backend.
The "Failed to fetch" error in the browser is a consequence of the failure in the POST request to the /signin endpoint of the "telegram.huly.app" service. The browser is unable to get a response from the server, resulting in a network failure (net::ERR_FAILED) and an error when trying to process the response (Failed to fetch).

Severity:
Critical. The inability to link Telegram directly affects the integrations functionality, which could be a key or highly used feature by Huly users. A downed integration service creates a very negative user experience and can impact the credibility and reliability of the Huly platform.

evidence: