gotify/server

"Failed to copy to clipboard" when trying to copy client key.

Opened this issue · 5 comments

Installed Gotify through Docker and I'm getting this error. The browser I'm using it Firefox but I've tried Edge too, in case it was a browser compatibility problem.

It may require HTTPS for it to work, this is a hard limitation (*) of the browser, if it is not HTTPS currently can you try it up or just copy manually?

Unfortunately I don't have https set up because I don't expose services outside of my network.

I forgot to add I can see and manually copy the token, it's just the button to copy that doesn't work.

Unfortunately I don't have https set up because I don't expose services outside of my network.

I forgot to add I can see and manually copy the token, it's just the button to copy that doesn't work.

I have https set up for all services, using dns-01 challenge and wildcard certificates.
Nobody needs to know the IP addresses of the services, and locally a pihole (now adguard home) rewrites all DNS requests to local IPs

You only need a domain name, no public servers.

Unfortunately I don't have https set up because I don't expose services outside of my network.
I forgot to add I can see and manually copy the token, it's just the button to copy that doesn't work.

I have https set up for all services, using dns-01 challenge and wildcard certificates. Nobody needs to know the IP addresses of the services, and locally a pihole (now adguard home) rewrites all DNS requests to local IPs

You only need a domain name, no public servers.

I don't see the need for any of this just to use https for internal services. For anything else, I have both Tailscale for hole-punching and Cloudflare Tunnel for those services I want to expose.

Additionally using https besides tunnels could guard against potential security vulnerabilities in the tunneling software.

The browser requires you to use https when you want to use certain apis including the clipboard api. There are some workarounds to get this working without https, but they are deprecated and I don't want them in this project.

An UX improvement could be to hide the button when it's an http connection, but I'm not sure it's worth the development effort, as most users use https.