Automation

 View Only

  • 1.  vSRX Native REST API Daemon (/rpc/) Throwing 404 - Serving J-Web HTML Login Fallback via Port 3000

    Posted 06-08-2026 07:08

    Hello everyone,

    Why do external REST API requests to my vSRX on port 3000 return a 404 with the J-Web HTML login layout instead of JSON data, what is the exact URI path schema required, and how do we prevent the web-management layer from overriding the native REST service daemon endpoints even though netstat confirms they are listening on separate ports (80 and 3000)?
    Any validation steps, logs paths under /var/chroot/rest-api/, or configuration corrections would be highly appreciated. Thank you..!!



    ------------------------------
    Narrala Homakiran
    ------------------------------


  • 2.  RE: vSRX Native REST API Daemon (/rpc/) Throwing 404 - Serving J-Web HTML Login Fallback via Port 3000

    Posted 06-08-2026 10:27

    Hi

    TCP Port 3000 is not available as one of the system service ports and so I would recommend using a port for the REST API that is listed under the host-inbound-traffic system-services configuration branch.  For Example: 'webapi-clear-text' (TCP 8080) and 'webapi-ssl' (TCP 8443) can be used for this scenario.  See the config example below...

    .remove j w eb config . remember to configure ssl or  rest https certificate . 

    set system services web-management http interface fxp0.0

    set system services rest http
    set system services rest control allowed-sources 0.0.0.0/0


    ------------------------------
    Anthony Abraham
    ------------------------------



  • 3.  RE: vSRX Native REST API Daemon (/rpc/) Throwing 404 - Serving J-Web HTML Login Fallback via Port 3000

    This message was posted by a user wishing to remain anonymous
    Posted 28 days ago
    This message was posted by a user wishing to remain anonymous

    test


    Original Message