All Products
Search

This Product

    Edge Security Acceleration:Troubleshoot common EdgeRoutine (ER) errors

    Document Center

    Edge Security Acceleration:Troubleshoot common EdgeRoutine (ER) errors

    Last Updated:Jun 18, 2026

    Fetch requests to the domain name of a routine not allowed

    Error message

    @Fetch.fetch: fetch authority is same with origin authority, which is forbidden

    Cause

    A routine cannot send fetch requests to its own domain name. For example, if the routine domain name is 1.a.com, the routine can fetch any other domain name but not 1.a.com itself.

    Internal status codes not allowed

    Error message

    HttpBody.constructor: invalid status code

    Cause

    Status codes 596, 597, 598, and 599 are reserved by EdgeRoutine (ER) and cannot be used in your code.

    Connection ended by ER

    Error message

    io error@: io error(Connection reset by peer)

    Cause

    The routine exceeded its CPU time slice limit, so ER terminated the connection and stopped the virtual machine (VM). An error log similar to the following is generated.

    2023 0306 16:39:39.611431 115939 JSThread-3() E @tag(JSError) @loc(src/js-instance-inl.h:366)]: <uid: debugger::I::79de2290-d3a3-4f89-81db-6c3ba779b8b2;event: fetch;host: ;path: /;auth: market.wapa.taobao.com;unique_id: ;pip: 127.0.0.1:46174;fetch_uuid: b5f59f33-8f9b-487d-be32-56e3c368f3f0;start_ts: 1678091979098;req: http;milestone: *-*---;><N/A><>: category: Fatal Error; caller: JSInstance; sub-reason: cpu time; description: N/A; message: the virtual machine has been forcebly terminated for user id 'debugger::I::79de2290-d3a3-4f89-81db-6c3ba779b8b2' due to its violation of resource constraints of system!

    Solution

    Increase the CPU time slice limit. For example, change the limit from 50 ms to 100 ms.

    No proxy address available

    Error message

    unhandled error(13485,13477)@: Error: io error@: no available fetch proxy address now\nstacktrace:\nN/A\n

    Cause 1

    The URL in the cache.put method uses https, which the cache API does not support. Change the URL scheme to http.

    Cause 2

    The fetch request targets a domain name that is not added to Alibaba Cloud CDN, but cdnProxy:true is set. Either add the domain name to Alibaba Cloud CDN or Dynamic Content Delivery Network (DCDN), or remove the cdnProxy:true configuration.

    Connection ended

    Error message

    Error: unhandled error(13486,13505)@: Broken connection, unexpected EOF

    Cause

    The upstream service closed the connection while the routine was still receiving response data.