You open Candy AI, type a message, and get a number instead of the chat: 1015, 500, “payment error”, “network error”. A rate limit and a declined card are different problems, and mixing them up is how people waste half an hour clearing cache when the block was at the bank.
This page sorts Candy AI errors by family, says who owns each one and gives the exact move, plus the ticket template that matches the service’s claims policy. It’s the troubleshooting counterpart to the full Candy AI review.
What errors Candy AI shows and what they mean
Candy AI runs on a site behind edge protection (Cloudflare) with an external payment gateway, which splits errors into four families: rate limiting, server failure, payment decline and client failure. Different owner, different wait.
| What you see | What it means | Whose fault | First action |
|---|---|---|---|
1015 / “You are being rate limited” | The site cut your requests because you passed its limit | The site’s rules, triggered by your volume | Wait 15-30 min without retrying |
500 / 502 / “Internal Server Error” | The server could not process the request | The server’s | Wait and check whether it is general |
| ”Payment error” / payment declined | The bank or the gateway won’t authorise the charge | Your issuer or the fraud checks | Retry and finish the 3DS window |
| ”Network error” in the APK or mod APK | The app can’t reach the service API | The client (unofficial build) | Go back to the browser |
| Endless loading screen | The site opens but the chat won’t connect | The client (cache, extension, network) | Try a private window |
The rule: homepage loads but the chat doesn’t? Client or session. Nothing loads? Server. Everything loads except payment? Your card issuer.
Code 1015 is not an account error
Cloudflare issues 1015 when the site has received too many requests from you in a short window. Its docs put it plainly: the site “has received too many requests and has temporarily blocked your access”. Not banned, slowed down.
500 is server-side, not your phone
A 500 or a 502 is a standard HTTP code: the request arrived, the server couldn’t answer it. Nothing you set in your browser makes a failing server stop failing.
Payment error is the most misread one
Three things get mixed here: a bank decline, the merchant’s fraud review and a region or currency mismatch. If the charge shows as CANDYAI.COM on your statement, it reached the gateway; if it doesn’t, it didn’t.
Error 1015: “You are being rate limited”
Most common, worst handled: people reload, log out, log back in, and the block gets longer. Retrying keeps it alive.
Why you’re the one getting it
Candy AI doesn’t publish its limiter threshold, but the triggers are recognisable: reloading in a loop when the chat is slow, four tabs open, a script firing automatic requests, and a VPN whose exit IP is a datacenter address shared by thousands.
How long it actually lasts
Cloudflare gives no fixed duration because it depends on the site’s rule, but its advice is specific: wait and come back later without burst-retrying, since retries “may extend the block”. Your own volume: 15 to 30 minutes; behind a datacenter VPN: 1 to 3 hours.
Getting out without making it worse
Close every tab and leave it alone for 20 minutes. Kill the VPN or switch to mobile data for a residential IP. If the block lines up with a corrupted session, clear cookies for that domain only.
Error 500 and 502: the server’s fault
500 is the most honest error here: not your fault, nothing to fix on your machine. 502 adds a layer — the proxy in front can’t reach the application server.
Confirming it isn’t your account
Open the site in a private window, then on another device and network. 500 there too? It’s the platform. Private window fine? Session or cache problem, not a real 500.
What to do while it’s down
Wait. Server failures get fixed in the infrastructure, not the client. Test every 10 or 15 minutes, not every 30 seconds: each retry hits the same limiter and can stack a 1015 on top.
When it’s worth a ticket
If the 500 runs over two hours and hits every network, open a ticket with the exact time, your country and a screenshot. Don’t delete the account or reinstall: neither touches the server.
Payment error: declined card or missing tokens
This is where the most money is lost through bad reactions. A declined payment retried five times can end in duplicate charges or a fraud block.
Four real causes of a decline
One, 3D Secure never completes: the bank window closes or times out and the payment reads as rejected, though no money moved. Two, the bank blocks the merchant by descriptor: the charge shows as CANDYAI.COM, a neutral label some issuers flag on the first attempt. Three, the merchant’s fraud review: the policy applies customer verification measures, so an odd pattern can leave the payment pending. Four, region or currency: with a VPN on, the purchase IP and the card’s country disagree.
| Method | Typical failure | What to do |
|---|---|---|
| Debit card | 3DS timed out or balance too tight | Retry and finish the bank window |
| Credit card | Blocked as adult merchant | Authorise the charge with your bank first |
| Prepaid card | Won’t accept recurring subscriptions | Use another card for the monthly plan |
| Wallet or mobile pay | Account region doesn’t match | Turn the VPN off, align account country and card |
| Any card, VPN on | Purchase IP is inconsistent | Switch the VPN off and pay again |
I paid and the tokens aren’t there
Charge on your statement, balance unchanged: don’t pay again. Wait a few minutes, then open a ticket with the receipt. Packs are stricter than subscriptions: no refund once a token from the pack is consumed. Claim before you spend.
What not to do with a failed payment
Don’t open a bank dispute before talking to support: the policy states that disputes judged unfounded can land you on a blocklist. A chargeback is the last card you play, not the first.
Network error in the APK or mod APK
The APK “network error” has a mechanical explanation: there is no official native Candy AI app in the stores, and the builds in circulation are web wrappers or third-party mods pointing at endpoints that change.
Why the mod fails at the network
A mod ships without the payment SDK and without current certificates. When the site rotates an API route or tightens its certificate, the old app keeps asking for the old path, and you get a network error that looks like your wifi and isn’t.
The risk you don’t see yet
A modified APK installs with broad permissions and no support channel: credentials pass through a third party, updates never arrive, the account can be closed for breaking the terms of service.
The alternative that actually works
Candy AI’s own site documents the shortcut: on iPhone, Share then “Add to Home Screen”; on Android, the browser menu then “Add to Home Screen”. A PWA shortcut with notifications, no APK and no mod. See the Candy AI mobile guide and the mobile experience comparison for what the mobile version can do.
Open Candy AI in your browser — the route that depends on no third-party build.
Candy AI won’t load or hangs on the splash screen
No error code: the page opens, the logo shows and the chat thinks forever. Almost always the client.
The private-window test
Open the service in a private window. Works there? Your profile: cache, cookies or an extension. Doesn’t? Move to the mobile-data test. Two steps that separate 80% of cases.
Extensions that break the chat
Ad blockers and aggressive privacy tools cut the persistent connections the chat needs to stream. If text appears all at once instead of typing out, disable the blocker for that domain.
Cache, cookies and local storage
The chat keeps state in the browser, and corrupted local storage produces sessions that look like they’re loading and never connect. Clear site data, not the whole browser: characters and history live in the account.
Networks that block the service
Corporate and school networks, plus some carriers with parental filters, block adult domains at DNS level. Works on mobile data but not on home wifi? The filter is in the router or the carrier.
5-minute diagnostic checklist
Work down and stop at the first step that explains the symptom.
- Open the service in a private window. Works? Your profile: cache, cookies or an extension.
- Does the homepage load while the chat fails, or does nothing load? Chat only points to the client.
- Note the exact error text:
1015,500,payment errorandnetwork errorare four different roads. - Turn the VPN off and repeat. If the 1015 disappears, the datacenter IP was the problem.
- Check your tokens before and after. Balance down and no message? That’s delivery, not payment.
- Take a screenshot with the system clock and your country visible.
- Decide: 1015 means wait without retrying; a 500 past two hours means a ticket; a payment failure, a ticket with the receipt.
A ticket support resolves in 24 hours
The claims policy fixes the channel and the details they expect. Getting them right changes how fast the answer comes.
The right channel
Support email is [email protected], and the policy also accepts the “Contact Us” area inside the service. Social media DMs are not official: no reference number, no response deadline.
What the policy requires
Full name and account email, the problem with the date and time of the incident, and screenshots. That’s what lets them match your case against the server records.
| Field | Example | Why it matters |
|---|---|---|
| Account email | the one you signed up with | Identifies the user without ambiguity |
| Date and time | 27/10/2026, 14:32 CET | Matches the failure to their logs |
| Exact error | 1015 after 3 reloads | Separates rate limit, server and payment |
| Browser and device | Safari 18, iPhone 15 | Rules out a client fault |
| Country and payment method | Spain, debit card | Explains a region-based decline |
| Screenshot | full screen, clock visible | Proves the state at that minute |
The deadlines the contract promises
Acknowledgement within 24 hours, with a reference number and the name of the person on the case; full resolution within 7 calendar days at most; and an escalation reviewed by someone outside the first decision.
Mistakes that slow a ticket down
Sending “it doesn’t work” with no screenshot, opening three identical tickets (that puts you at the back of the queue), leaving out country and payment method, mixing a payment error with a chat error.
What fixes nothing and can cost the account
Five forum recipes that at best achieve nothing.
Reinstalling the browser
It touches neither the site limiter nor the server. At most you sign in again and reconfigure extensions.
”Free token generators”
There is no public token API. Sites promising tokens for your email and password are credential phishing, and a compromised account can be used to get around the service’s limits.
Free VPNs as a fix for 1015
They make it worse: free VPNs pile thousands of users onto the same datacenter IPs, the ones that hit rate lists first.
Chargeback as a first response
The policy warns that unfounded disputes can end in a blocklist. A chargeback closes the door; a ticket leaves it open.
A new mod APK
The network error comes from the unofficial build itself. Swapping mods swaps the symptom, not the cause.
FAQ — Candy AI
Why do I only get error 1015 on Candy AI and not on other sites?
Because each site configures its own limiter. Candy AI applies rate rules to the requests it receives, and your normal browsing doesn’t pass other services’ thresholds. That domain’s policy, not your connection.
Does error 500 mean my account was deleted?
No. A 500 is a server failure while processing a request, not an action on your account. A restriction would show a specific account or sign-in message.
I paid, I have no tokens and the charge is there — do I wait or open a ticket?
Open a ticket with the receipt and don’t pay again: retrying a charge that already went through is the fastest route to a duplicate or a fraud block. Packs have a tighter refund window than the subscription, so claim before you spend.
Does a VPN fix or worsen Candy AI errors?
It worsens 1015 and can trigger a payment error. Free VPNs hand out shared datacenter IPs, the first to fall under rate rules, and paying with the VPN on makes your purchase IP disagree with your card’s country.
Does the mod APK solve the “network error”?
No. The unofficial build points at old API routes or loses the service certificates. What works is the web version added to your home screen, the method the platform documents for iOS and Android.
How long does support take to answer?
Acknowledgement within 24 hours, with a reference number and a case owner, and full resolution within 7 calendar days at most. If the first ticket misses that, ask for an escalation.
Do I lose my characters if I clear the browser cache?
No. Characters, history and tokens live in your account, not the browser. Clearing site data only signs you out and wipes the local state behind the loading screen.
If the problem was price rather than a technical fault, the plan breakdown is in the Candy AI pricing guide. If you no longer want the charge, the procedure is in the refund and cancellation guide.
- Candy AI APK: what’s legal and what isn’t
- Candy AI mobile experience: web app vs APK
- Candy AI mobile guide 2026
- Candy AI pricing 2026: plans, tokens and real cost
- Candy AI refund and cancellation
- Candy AI: is it safe and private?
- Checklist for choosing a safe AI girlfriend app
- Candy AI free trial: what you actually get
Try Candy AI in the browser — the route that skips the APK, the mod and the network errors.