If you register or log in during local development and then switch to your deployed app, you may see authentication errors even though everything worked locally. The local dev server signs tokens with a local secret. Your deployed app uses a different secret, so it rejects local tokens.To fix the issue, sign out of your local session or delete your tokens from your local browser storage and then log in through your deployed app. The deployed app issues a new, valid production token.
If you’re using an AI coding agent, the base44-troubleshooter skill teaches it to fetch and analyze your backend function logs automatically. Ask your agent something like “show me all errors from the last hour” and it will pull the relevant logs, identify patterns, and suggest fixes.For manual debugging, use the logs command to view function output, errors, and timing information. You can filter by function name, log level, and time range.
If calls that a backend function makes to Base44 fail with a 403 error and the message “The domain’s DNS records point to a prohibited IP address”, the function is too deep in a chain of functions calling each other. Retrying the call doesn’t help. See Function chain limit for the limit and how to restructure the chain.
