Copied message links use fluxer.app instead of web.fluxer.app and open a 404 page

(#438) Bug Fixed messaging

Summary

when using 'Copy Message Link' on a message it results in a message link like this: https://fluxer.app/channels/1427764813854588940/1427764813854588943/1484577625735422682 this works when embedded on the fluxer client app but when sent externally via a third party, the link 404s on Fluxer's website instead of bringing you to a message, this is fixed if you prefix the message link with web. such as: https://web.fluxer.app/channels/1427764813854588940/1427764813854588943/1484577625735422682

Steps to reproduce

  1. Right click a message in Fluxer and click the 'Copy Message Link'
  2. Paste in external platform, such as directly in a browser
  3. You will be presented with a 404 page (or presented with a 404 after clicking the link from an external platform such as another chatting app)

Merged posts

These posts were merged into this one. Their comments are now part of the conversation below, marked with where they came from.

Merged from #498 404 Error on Valid Message Link Redirection (Routing Issue)

RexSystemoriginally by @ataraksiya on GitHub

Report details

Summary

When a "Message Link" is copied and pasted into a browser, the application fails to resolve the URL and triggers a 404 error, even though the URL structure in the address bar appears correct. Impact: This is a significant functional bug that breaks the core navigation and sharing experience. Users are unable to reference or share specific messages externally, leading to a loss of context and poor user retention. Realistic Scenario: A user shares a direct link to an important announcement or a specific message with a friend. When the friend clicks the link, they are met with a 404 error page instead of the intended content, making the "Copy Message Link" feature useless.

Steps to reproduce

Step 1: Open Fluxer on the web client using Google Chrome. Step 2: Right-click any message in a DM or Server and select "Copy Message Link". Step 3: Paste this link into a new browser tab or an Incognito window. Observed Behavior: The browser shows a 404 error page (as seen in the attached screenshot). Expected Behavior: The platform should resolve the path (e.g., /channels/@me/...) and display the specific message.

Environment (optional)

stable build 277 (e0b277d), 2026-04-10 20:35:44 UTC, Chrome 146.0.0.0, Windows NT 10.0 (x64)

Logs or screenshots (optional)

Root Cause Analysis: The issue is specifically caused by the missing web. prefix in the generated URL.
  • Current (Broken) Output: https://fluxer.app/channels/1427764882469228556/1427764882469228559/1492307747926921254
  • Correct (Working) URL: https://web.fluxer.app/channels/1427764882469228556/1427764882469228559/1492307747926921254
The function generates the link without the web. subdomain. If the prefix is manually corrected, the routing works perfectly. The fix should involve updating the string generator in the "Copy Message Link" function to include the correct subdomain. Proof: I have attached screenshots showing the exact 404 error page while the message URL is still present in the address bar. I have also tested this in Incognito mode and cleared my cache/cookies to ensure this is not a local client-side issue. image image image
  • 576851647-806ee1b8-88e6-4ab9-b826-f9d711ab8d58.png

    576851647-806ee1b8-88e6-4ab9-b826-f9d711ab8d58.png

    1365×691 | 46 kB

  • 576851662-50dc60a5-23cc-4dcf-9a40-77f6466c28c7.png

    576851662-50dc60a5-23cc-4dcf-9a40-77f6466c28c7.png

    1365×729 | 48 kB

  • 576870345-0f983440-f411-415d-946e-a6ae8fb4724c.png

    576870345-0f983440-f411-415d-946e-a6ae8fb4724c.png

    1365×689 | 163 kB

1 comment

Sign in with Fluxer to comment and vote.
Comment by ternera
terneraMod 1 vote Merged from #498 originally by @ternera on GitHub
Can reproduce this. The link is clickable when you paste the URL back into a Fluxer channel, but not if you try to visit the URL directly (because it's fluxer.app instead of web.fluxer.app). canary build 275 (3646cf4), 2026-04-10 20:26:51 UTC, Chrome 147.0.0.0, macOS (arm64)