Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

clipboard not working on docker selfhosted app #170

Open
clacalderonc opened this issue Jul 15, 2023 · 4 comments
Open

clipboard not working on docker selfhosted app #170

clacalderonc opened this issue Jul 15, 2023 · 4 comments

Comments

@clacalderonc
Copy link

clacalderonc commented Jul 15, 2023

Hi Team,

When i use the self hosted version of the app, the clipboard button for chat content (or markdown code blocks) doesn't really work at all.

Self hosted:
image

chatwithgpt.ai

image

i'm using the latest docker image available, tried on chrome, edge, firefox, same result, no errors on browser console.

Rergards.
Claudio

@cogentapps
Copy link
Owner

cogentapps commented Jul 15, 2023

Thanks for reporting this. Just to confirm, are you using the release branch of the docker image (docker pull ghcr.io/cogentapps/chat-with-gpt:release)?

@clacalderonc
Copy link
Author

clacalderonc commented Jul 16, 2023

Thanks for reporting this. Just to confirm, are you using the release branch of the docker image (docker pull ghcr.io/cogentapps/chat-with-gpt:release)?

yes, using the release tag and just to be sure I recreated the environment several times, i made this small docker-compose to handle my env.

version: '3'
services:
  app:
    image: ghcr.io/cogentapps/chat-with-gpt:release
    ports:
      - 3000:3000
    volumes:
      - ./data:/app/data

@cogentapps
Copy link
Owner

Most likely because many browsers block copying on 'insecure' connections (no SSL) and the Docker command doesn't use SSL by default. We have experimental support for enabling this in ./data/config.yaml:

tls:
  selfSigned: true

but it’s currently untested and may not work. See discussion in #132 for another possible approach.

@clacalderonc
Copy link
Author

Most likely because many browsers block copying on 'insecure' connections (no SSL) and the Docker command doesn't use SSL by default. We have experimental support for enabling this in ./data/config.yaml:

tls:
  selfSigned: true

but it’s currently untested and may not work. See discussion in #132 for another possible approach.

Great, I enabled that option and issued a letsencrypt certificate and is working now, I saw that the selfSigned option try to use a script that is not present on the image (generate-self-signed-certificate.sh).

Anyway, you can put cert.pem / key.pem files in data/ directory, plus the self signed option enabled and ssl it's working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants