Chaging server URL in openapi did not actually change the URL

GPT builders Plugins / Actions builders
1

I am a creator of Scholar Assist, a ChatGPT plugin for academic researchers.

I want to update the plugin API from “https://scholarassist.org” to “https://plugin.scholarassist.org” (subdomain), so that I can host the landing page at https://scholarassist.org.

So I updated the openapi spec from

openapi: 3.0.2
info:
  title: Scholar Assist
  description: Searches relevant academic papers and answers any specific question from the papers.
  version: 1.0.3
  servers:
    - url: https://scholarassist.org

to

openapi: 3.0.2
info:
  title: Scholar Assist
  description: Searches relevant academic papers and answers any specific question from the papers.
  version: 1.0.3
  servers:
    - url: https://plugin.scholarassist.org

and deployed the plugin again. However it didn’t change the server domain. I contacted the OpenAI team about this, but am wondering if anyone else managed to update the server URL, or knows how to fix this.

2

Hi @kiyo921

Every plugin requires a ai-plugin.json file, which needs to be hosted on the API’s domain. For example, a company called example.com would make the plugin JSON file accessible via an https://example.com domain since that is where their API is hosted.
-Docs on Plugin Manifest

Also the openapi spec you shared isn’t indented correctly. YAML files are sensitive to indentation.

Here’s the correctly indented file snippet:

openapi: 3.0.2
info:
  title: Scholar Assist
  description: Searches relevant academic papers and answers any specific question from the papers.
  version: 1.0.3
servers:
  - url: https://join.scholarassist.org
1 Like
3

Thank you for the response. Indentation was my mistake on copy/paste, I’ve just fixed it in the original thread.

My question was about how to host the plugin in a subdomain, which I believe is possible since company like Expedia is using https://www.expedia.com/ for their landing page and uses the sub domain https://apim.expedia.com to host the Expedia plugin (according to ChatGPT Plugin - Expedia | GPTStore.ai). So I wanted to know how to change from hosting my plugin from https://scholarassist.org to https://plugin.scholarassist.org similar to Expedia plugin.

4

When you mention hosting, do you imply you want to know about hosting on server side, or pointing the plug-in to the subdomain?

5

Yes, this is the current status

  1. The domain for my ChatGPT plugin (fastapi backend): https://scholarassist.org

And I want to change it to the following

  1. The domain for my ChatGPT plugin (fastapi backend): https://plugin.scholarassist.org
  2. The landing page (nextjs frontend running in a different server: https://scholarassist.org

The problem is that https://scholarassist.org is currently used by the chatGPT plugin, so even when I updated the openapi.yml as follow

openapi: 3.0.2
info:
  title: Scholar Assist
  description: Searches relevant academic papers and answers any specific question from the papers.
  version: 1.0.3
  servers:
    - url: https://plugin.scholarassist.org

The plugin backend seems to be hosted at https://scholarassist.org, and not https://plugin.scholarassist.org, so https://scholarassist.org is not available for me to host the frontend server.

So I would like to understand the process of changing the domain for running the plugin backend server.

6

AFAIK, this should be be simple to do. In my knowledge, the following step should help you get the job done.

  1. Update DNS Records:

    • Add a new subdomain plugin.scholarassist.org
    • Point the subdomain to the Fast API endpoint.
    • Ensure that the main domain scholarassist.org points to the IP address of the server where your Next.js frontend will be hosted.

  2. Configure Your Web Servers:

    • On the server where your ChatGPT plugin backend is hosted:
      • Update the server configuration to recognize plugin.scholarassist.org as the domain for the ChatGPT plugin backend. Make sure your plugin manifest ai-plugin.json and OpenAPI spec are updated for the new subdomain.
      • Ensure that the server is set up to respond to requests for plugin.scholarassist.org.
    • On the server where your Next.js frontend is hosted:
      • Set up the server to respond to requests for scholarassist.org.

  3. Update SSL Certificates

  4. Update Application Configuration:

    • In your ChatGPT plugin backend configuration, ensure that any references to the domain are updated to plugin.scholarassist.org.
    • Update any other configurations, environment variables, or settings that reference the old domain.

  5. Test the Changes:

    • Once you’ve made the above changes, test both https://plugin.scholarassist.org and https://scholarassist.org to ensure they’re working as expected.
    • Check for any mixed content warnings or SSL certificate issues and resolve them.

  6. Update External References:

    • If there are any external services, applications, or users that reference https://scholarassist.org for the ChatGPT plugin backend, inform them of the change and provide the new https://plugin.scholarassist.org URL.

  7. Test the changes.

1 Like
7

Did the changes above work? I have the exact same problem → want to host the api and config files on plugin.mydomain.com instead of mydomain.com.