Cannot copy invite link from Members page

[darestov]

Bug description

Hello!
I want to invite a user by sending him an invite link. I created the invitation (pending) and when I hit the "Copy invite link" button, nothing was copied and an alert "Failed to copy invite link" was shown. No web requests, no errors in console.

Version information

• Signoz version: 0.115
• Browser version:
• Your OS and version:
• Your CPU Architecture(ARM/Intel):

Additional context

I was able to copy invite links in SigNoz v0.110.

[SagarRajput-7]

@darestov - to further investigate and reproduce this issue, I would require a few pieces of information from your end, as this is working fine on multiple other platforms with the same Signoz version you mentioned.

• Browser & OS: info & version
• How are you running Signoz? - local or deployed

Why do I need these? - Since for this copy we are using Native Web API - navigator.clipboard provided by browsers.

Lastly, are you able to use other copy functions in the app?

• like one example you can find at the
  • Password Reset Link: Active Member --> click on --> Generate Password Reset Link

[darestov]

@SagarRajput-7
Browser: Yandex Browser 26.3.0.2166 (Chrome based) , also reproduces in vanilla Chrome 146.0.7680.80.
OS: Windows 11 25H2 (26200) 64bit

I run Signoz in Docker (free license).

Active Member --> click on --> Generate Password Reset Link
Ends up with this (failure):

At the same time, Copy Field Value (from span) works well, I'm able to paste it elsewhere.

[SagarRajput-7]

@darestov ,

Using a private IP (10.155.36.20***) over HTTP... the browser disables the navigator.clipboard object. As all browser native methods require a secure context - (Refer)

To fix this:

• use HTTPS
• You can also try the flag approach with chrome://flags/#unsafely-treat-insecure-origin-as-secure bypass. It allows you to manually whitelist a specific insecure origin (e.g., http://10.155.36.20***) so the browser treats it as a secure context.

[AayushKrGupta]

Hi! I looked into this issue and it seems related to how clipboard APIs work in browsers.

The current implementation uses navigator.clipboard.writeText(), which only works in secure contexts (HTTPS or localhost). When running SigNoz over HTTP (e.g., private IP), the Clipboard API becomes unavailable, leading to the "Failed to copy invite link" behavior without any console errors. :contentReference[oaicite:0]{index=0}

So this appears to be expected browser behavior rather than a bug in SigNoz.

Proposed improvement:
Instead of failing silently, we could improve UX by:

1. Detecting clipboard availability using:
   if (!window.isSecureContext || !navigator.clipboard)

2. Showing a clear message or tooltip like:
   "Copying requires HTTPS (secure context)."

3. Optionally adding a fallback using document.execCommand('copy') for better support in HTTP environments.

This would help avoid confusion for users running SigNoz locally over HTTP.

Happy to work on this if this approach sounds good!

[darestov]

Thanks for the answers! I'll be trying to implement HTTPS. But - copying text from span attributes, for example, still works. How is that?