Wispbyte Support Request – HTTP 403 Blocking Python API Access

Posted by user_3il023 in websites.

Hello Wispbyte Support Team! I'm experiencing an issue with automated HTTPS access to my Python server hosted on Wispbyte. Server details: Server: autonomia telegram Node: FREE EU RO 12 Subdomain: https://autonomia telegram.wispbyte.app Application port: 16398 Plan: Free Hosting Problem: My Python application is running successfully, and the HTTPS API is accessible through a web browser. When opening: https://autonomia telegram.wispbyte.app/v1/health the browser correctly receives HTTP 401 with: However, when accessing the same endpoint using a standard Python HTTPS client, the request receives HTTP 403 from Cloudflare/Wispbyte before reaching my application. CF Ray: a563a0dd5cf24db3 FRA The API uses its own Bearer token authentication to protect access. Could you please help with the following? 1. Identify which Cloudflare or Wispbyte security rule is blocking legitimate Python HTTPS requests. 2. Confirm whether machine to machine HTTPS API access is supported on the free hosting plan. 3. If supported, advise how to enable it without disabling HTTPS verification or application authentication. I also experienced intermittent access issues with the Wispbyte control panel and community forum, including false ad blocker detection despite disabling browser protections. I would appreciate your help resolving these issues without reinstalling the server or losing existing data. Thank you for your assistance!

Replies

Byte (AI assistant)

This looks like an edge security block on the Python request, not an application authentication failure: the browser’s 401 shows your API is responding, while the Python request’s 403 appears to happen before it reaches the app. A CF Ray ID alone doesn’t identify which rule triggered it. Machine to machine HTTPS access is supported. Keep certificate verification enabled and your Bearer token private. Try: 1. Check that your Python client sends the exact same URL and method, and isn’t following a redirect to a different host. 2. Send the Python code you use (with the token removed), the 403 response body and headers, and the approximate time of the request to the Wispbyte Discord so the edge block can be investigated using the Ray ID. 3. Don’t reinstall the server; that won’t resolve an edge security rule. The control panel ad blocker detection is a separate issue.

user_3il023

Thank you for your response. Unfortunately, the issue is still not resolved. My Python HTTPS client continues to receive HTTP 403 from Cloudflare/Wispbyte, while the browser receives the expected HTTP 401 from my application. Could a human support team member please investigate the Cloudflare security block and advise how to allow legitimate automated API requests on the free hosting plan? I would appreciate your assistance. Thank you!

Related discussions

Wispbyte Community Forum