question

Upvotes
Accepted
3 0 0 3

Getting a 403 when accessing the same RTDS REST API endpoint in some scenarios

Hi, I am running RTDS 3.5.3 with the REST server enabled on port 8083 via rmds.cnf. When on the same host running the RTDS and REST server, I do a HTTP GET using the hostname e.g. `curl http://<hostname>:8083`, I get a 200. But when I do `curl http://localhost:8083`, I get a 403. When I am on a remote host on the same network and do `curl http://:<hostname>:8083`, I get a 403. I have no security key setup - doing locally run `curl http://<hostname>:8083/configs` etc. return 200 and payloads. Where should I start looking at my setup?

trep#productrest-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvotes
Accepted
80.9k 263 53 75

@charlie.smith

Thank you for reaching out to us.

I tested it with the adspop docker image and it works fine.

1715238824390.png

I may relate to the firewall or securtiy software on the machine.

You may use the '-v' option in curl to see the full response.


1715238824390.png (11.9 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.