acedogblast

I see a repeating POST and OPTION requests on the network monitor to `http://127.0.0.1:45456/start`. I have attached a screenshot and the HAR file. [127.0.0.1_Archive [24-03-12 15-45-06].har.gz](https://github.com/httptoolkit/httptoolkit/files/14577924/127.0.0.1_Archive.24-03-12.15-45-06.har.gz)  EDIT: The console...

Running `echo $HTTPTOOLKIT_SERVER_BINPATH` gives me nothing and I have no memory of ever creating such ENV. Is it possible that the npm packages I am using is causing this problem?...

Opening `app.httptoolkit.tech` does work.

I do not have any other servers/VMs/Docker container on the laptop. Netstat and PS tree tells me that only httptoolkit from the git clones are operating on the associated ports....

This is what I get when appending to constants.ts ``` console.log(ALLOWED_ORIGINS) console.log(MOCKTTP_ALLOWED_ORIGINS) ``` ``` [ /^https?:\/\/localhost(:\d+)?$/, /^http:\/\/local\.httptoolkit\.tech(:\d+)?$/, /^https:\/\/app\.httptoolkit\.tech$/ ] [ /^https?:\/\/localhost(:\d+)?$/, /^http:\/\/local\.httptoolkit\.tech(:\d+)?$/, /^https:\/\/app\.httptoolkit\.tech$/, 'chrome-extension://oeehdgfohghfelggpifolochpnkdmpog' ] ```

Using `localhost:8080` still results in the same issue even after the 2 blocks you mentioned. The server does now give me an output of the mock session starting after removing...

OK I will look into. Have you been able to reproduce the issue on your side?

I just tested on a different linux computer which works. The only reason why it is different is that the laptop (which did not work) is using a Snap version...

What probe is "PicoProbe"? It it just a Raspberry PI Foundation's Pico line of RP2040 dev boards flashed with the Raspberry Pi Debug Probe firmware?

Changed to shorten the text per your suggestion. So Rusty Probe firmware already has SWO and UART support? That means the firmware TODO list needs updating as well.