Yes, same for me
until the time is 300 the error stile at http 1003
Yes, same for me
until the time is 300 the error stile at http 1003
Hi! I understand the desire to roll back to a time when "everything worked and didn't buzz," but it's like a favorite bar that's closed for renovation, and the "deepseek-chat" sign is no longer lit. DeepSeek has officially retired the old model, so version 1.4 from message #54 will now knock on a closed door and receive an HTTP 400, which is no better than 1003, just another sad number.hi
this error not exist in the previous version. perhaps backup to this one !
give setting please
So based on this , the EA just active on NY Session ?It seems that we have not an isolated case here, but a direct flash mob "HTTP 1003"! The DeepSeek server apparently decided that Doomsday had come and turned on the "fortress siege" mode for everyone at once.
It happens when DeepSeek has a global glitch, or they massively shake up access rules, and half of the users become "suspicious" simply for breathing.
What to do while they fix their neurons there:
• Don't change keys like crazy — it won't help, you'll only hit the limits. One key for everything.
• Check the SpikeCooldownSec in the settings — if it is too small (like 5 seconds), the server thinks that you are attacking it. Hold at least 300 (5 minutes) — let the neural network digest the previous query.
• Try a VPN or IP change — sometimes Cloudflare bans a specific range of addresses, not you personally. Moving to another country can virtually solve the problem.
• Look at the DeepSeek status (if they have a status page) - perhaps they are honestly writing there: "We've fallen, wait."
Well, remember: if the neural network does not respond, it does not mean that it does not love you. It's just that it's "Monday" for her. We are waiting for DeepSeek to stop acting up. Patience and green candles for everyone!
Can we not use Phyton to do so, instead of relying on Deepseek engine?Hi! I understand the desire to roll back to a time when "everything worked and didn't buzz," but it's like a favorite bar that's closed for renovation, and the "deepseek-chat" sign is no longer lit. DeepSeek has officially retired the old model, so version 1.4 from message #54 will now knock on a closed door and receive an HTTP 400, which is no better than 1003, just another sad number.
We've moved to the new model because the old entrance has been closed. It will be easier to use deepseek-v4-flash now — it's really less picky. I can't say how soon, but I'll finish the version where you can choose between deepseek-v4-pro and deepseek-v4-flash.
So the rollback is a ticket to the depot, not to profit.
You're absolutely right — Python is like a Swiss army knife with a laser sight for analysis and neural networks: flexible, powerful, a library wagon. But I deliberately went through the "all in one" on MQL5, and here's why:Can we not use Phyton to do so, instead of relying on Deepseek engine?
settings/analysis in Py, trade taken surely use MT5
Dear samshoshoEA, I think I am beginning to suspect that you are a very persistent AI bot that is testing my convergence response.For XAUUSD robots, I usually check whether the strategy depends on trend strength, spread widening, and session timing. A backtest alone can look good, but forward testing should confirm whether entries survive real broker execution, especially during news and low-liquidity hours. What conditions are you using to decide when the robot should stop trading?