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

Integrating Kaguya as a GPTs Action Due to HTTP/HTTPS Mismatch #44

Open
goldengrape opened this issue Nov 12, 2023 · 1 comment
Open

Comments

@goldengrape
Copy link

I am attempting to integrate Kaguya with GPTs as an action, but I am encountering an issue related to the HTTP and HTTPS protocols.

Steps to Reproduce:

  1. I ran the Kaguya plugin and successfully accessed it at http://localhost:3000.

  2. I copied the contents from http://localhost:3000/openapi.yaml and pasted it into GPTs actions.

  3. Upon doing so, I received the following warnings:

    Warnings
    None of the provided servers is under the root origin https://localhost
    Server URL http://localhost:3000 is not under the root origin https://localhost; ignoring it
    

Issue:
It appears that there is a protocol mismatch issue, as Kaguya is running on HTTP and GPTs actions seem to require HTTPS. As a result, the server URL is being ignored due to not being under the root origin https://localhost.

Questions:

  1. Has anyone successfully integrated Kaguya as an action in GPTs?
  2. Although Kaguya is originally intended as a ChatGPT plugin, I believe there should be a close similarity in its integration with GPTs. If it is indeed feasible to run it as a GPTs action, how should the yaml be modified to address the HTTP/HTTPS protocol mismatch?

Any guidance or suggestions on resolving this issue would be greatly appreciated. Thank you for your support and for the development of this innovative tool.

Best regards,

@nailuoGG
Copy link

You should deploy your service to the public internet

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