This is a list of frequently asked questions about Express Mode.
You exceeded your current quota
Q: I am getting “You exceeded your current quota, please check your plan and billing details.” What should I do?
A: This message coming from OpenAI and it’s not related with the plugin. It means that you have consumed all the credits or units allocated to your plan and have reached the limit of your billing cycle.
Please note that having ChatGPT Plus subscription and having OpenAI API credits are two different things. The API usage comes with its own charges.
To resolve this issue, you need to add more credits to your OpenAI account.
Please follow below steps:
- Go to https://platform.openai.com/account/billing/payment-methods and add a new payment method.
- Once payment method is added, please go to https://platform.openai.com/account/api-keys and generate new api keys.
- Now paste this new api key under the plugin Account – API Key.
You can check your current usage at https://platform.openai.com/account/usage.
Timeout issue
Q: I am getting “It appears that your web server has some kind of timeout limit. This can also occur if you are using a VPS, CDN, proxy, firewall, or Cloudflare. To resolve this issue, please contact your hosting provider and request an increase in the timeout limit.” message. What should I do?
A: It means that your server have timeout limitation or your organization is being rate limited by OpenAI.
Rate Limiting
OpenAI’s new rate limit documentation may provide indirect hints about the issues many accounts face.
Is your GPT models running slow? Consider the following:
- Are you currently on a prepay plan?
- Have you paid OpenAI over $50 in prepaid credits, over a week ago?
Reaching new “tiers” for prepay credit users seems to be related to these criteria. The quality of service you receive might be tied to the non-refundable money you’ve given to OpenAI. They “may” move you to a lower latency depending on this.
What to do next:
- Visit your account’s rate limits page.
- Check if you’ve been assigned one of the new unique rate limits of 20000 or 40000 tokens per minute. If you have, it indicates you’re in a lower “tier”.
- Remember, OpenAI has mentioned they wouldn’t consider any rate request form for an increase of the GPT-4 TPM rate of 10000 that’s been allocated to new users. If you’re wondering about the criteria, it’s made clear on that page: PAY UP.
- Go to https://platform.openai.com/account/billing/payment-methods and add a new payment method.
- Once payment method is added, please go to https://platform.openai.com/account/api-keys and generate new api keys.
- Now paste this new api key under the plugin Account – API Key.
So, in summary, if you are experiencing timeouts, it likely means you are in a lower tier either because you haven’t added your credit card or your credit is below $100, resulting in OpenAI rate limiting your requests.
Server-Specific Timeouts
If you’ve already added your credit card to OpenAI, ensured you’re not in a lower tier, and you’re still experiencing timeouts, this indicates server restrictions or configurations that might be affecting your connection.
Apache
If you are using Apache:
- The timeout value can be found in the
httpd.conf
file. You might need to search for the Timeout directive in this file. - Increase the value as required to give your scripts or processes more time to complete.
- If you don’t have the necessary permissions to edit this file or aren’t comfortable making changes, please contact your hosting provider for assistance.
Nginx
If you are using Nginx:
- The timeout values are often found in the
nginx.conf
file. - You can adjust the
fastcgi_read_timeout
value in the location block that handles PHP requests:
location ~* /MAMP([^-].*)$ {
root /Applications/MAMP/bin;
index index.php;
location ~ \.php$ {
try_files $uri =404;
fastcgi_pass unix:/Applications/MAMP/Library/logs/fastcgi/nginxFastCGI.sock;
fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
include fastcgi_params;
fastcgi_read_timeout 600; # Adjust this value based on your needs
}
}
- You can also append below values in /etc/nginx/conf.d/timeout.conf file.
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
php.ini
Regardless of the web server you are using, PHP has its own execution timeout setting which might be causing the issue:
- Locate your
php.ini
file. Its location can vary based on your server setup and PHP installation. - Find the
max_execution_time
directive and adjust the value. For instance:
max_execution_time = 1000 ; Adjust to the number of seconds you need
- Save the php.ini file and restart your web server and PHP service for the changes to take effect.
Always remember to backup configuration files before making changes. If you’re on shared hosting or don’t have access to server configurations, please contact your hosting provider.
cPanel
If you are using cPanel, there might be an issue with PHP-FPM configurations. You can refer to the official cPanel documentation or this link for troubleshooting and guidance.
Plesk
For those using Plesk, the timeout settings can be adjusted through the Service Plans or Subscriptions settings. Navigate to the PHP settings section and adjust the max_execution_time
value as needed. If you don’t have administrative access, please contact your hosting provider for assistance.
You can find more information in this link.
CloudFlare
If you are using CloudFlare, their default timeout limit is 100 seconds. Which means you won’t be able to generate content if content generation exceed 100 seconds. You can upgrade your plan with CloudFlare or disable their service or you can reduce number of headings for content generation.
.htaccess File
You can learn how you can edit max execution value using .htaccess file in this link.