Troubleshooting

Replies appear all at once instead of streaming

Something between the server and the browser is buffering the response. Max Harness asks Nginx not to buffer, but a second proxy or CDN may still do it. Turn off response buffering and compression for text/event-stream, or bypass the CDN for paths under /app/api/.

A reply stops after about a minute

A proxy read timeout is cutting the connection. Raise proxy_read_timeout or fastcgi_read_timeout to 300 seconds or more. Long answers from reasoning models can take several minutes.

"The request failed (413)" when uploading

The file is larger than the web server or PHP accepts. Raise upload_max_filesize and post_max_size in the PHP settings and client_max_body_size in Nginx. In CloudPanel these are on the site's Settings page.

A provider test fails

Read the message under the provider. It includes the provider's own explanation. The most common causes are a mistyped key, an account without billing set up, and a key created for a different product, such as a coding plan key used on the general endpoint. See the table in Connect a provider.

"Could not connect" for a provider

The server could not reach the address at all. Check the base URL and that outbound HTTPS is allowed by the host's firewall. For Ollama, remember the address is resolved from the server.

A model returns an error about temperature or another parameter

Open the generation settings for the conversation and clear the field. Some models accept only their default values.

Images or files are rejected

The selected model does not accept that input. Pick a model with the Images badge, or correct the capability under Providers, Models, Details if the provider reports it wrongly.

Password reset emails do not arrive

Outgoing email is not configured or the SMTP details are wrong. An administrator can check under Admin, System with Send test email. Until it works, an administrator can help a user by verifying their email in the user list. There is no way to read or set a user's password from the admin panel.

Locked out of two-factor authentication

Use a recovery code in place of the authenticator code. If you have none, an administrator with database access must clear the two_factor_secret, two_factor_recovery_codes and two_factor_confirmed_at columns for the account.

The installer says the configuration cannot be written

The web server user cannot write to the application folder. Fix the ownership so the site user owns all files, then reload.

The installer says the database already contains tables

Use an empty database. If you are restoring an existing installation, put back your original .env file and storage/installed.lock instead of running the installer.

A blank page or "500" error

Look at storage/logs/laravel.log through the File Manager. The last entry names the problem. A common cause after moving servers is a missing PHP extension.