TRPEndpoint not shown in the interface, even though it is set.

[ping-localhost]

At /about the TRP Endpoint is shown as N/A, even though it is set in the env. In fact, TRPEndpoint seems to not be used anywhere in the code.

[daniellemaxwell]

@ping-localhost The N/A value for TRP Endpoint on the About page is currently a hardcoded value. We will remove the need to have separate TRISA AND TRP endpoints soon. Once the changes are merged, we'll follow up and let you know.

[ping-localhost]

@daniellemaxwell Has this change been merged already and released? We are seeing the following:

{"level":"warn","path":"/","ser_name":"trp","version":"0.27.1-beta.33 (a8a5eb7)","method":"GET","resp_time":0.161824,"resp_bytes":83,"status":404,"client_ip":"87.236.176.241","request_id":"01JH50VGHEM30E9VQDAAWZ67ND","severity":"WARNING","time":"2025-01-09T07:53:23Z","message":"trp GET / 404"}

A 404 does not seem like something we want. The node switched to TRISA, but we do need to be able to get TRP messages.

[bbengfort]

@daniellemaxwell Has this change been merged already and released? We are seeing the following:

{"level":"warn","path":"/","ser_name":"trp","version":"0.27.1-beta.33 (a8a5eb7)","method":"GET","resp_time":0.161824,"resp_bytes":83,"status":404,"client_ip":"87.236.176.241","request_id":"01JH50VGHEM30E9VQDAAWZ67ND","severity":"WARNING","time":"2025-01-09T07:53:23Z","message":"trp GET / 404"}

A 404 does not seem like something we want. The node switched to TRISA, but we do need to be able to get TRP messages.

@ping-localhost unfortunately the fix is not merged in quite yet; we need to move to a system that has only one endpoint for everything rather than 3 in order to make the travel addresses work; but that came with a few unseen complications. Are you using the webhook? I can wire something up that would have incoming messages get passed to the webhook; but they might not appear in the UI or in the API; would that work as a temporary solution for you to start receiving messages right away?

[ping-localhost]

We are currently using the API to fetch all the data we need (so it missing from the API would be a deal breaker right now). The webhook is not being used.

[bbengfort]

Alright - let me see if I can get something together for you next week - I don't want you to be blocked by the one port thing!