You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Fledge v2.6.0 with the HTTP South services and trying to send data to multiple HTTP South service endpoints using the same port. However, the data is not being published to the other HTTP South services, and encountering a 404 error.
Steps to Reproduce:
Set up Fledge v2.6.0 and configure the HTTP South plugin to send data to multiple endpoints using the same port.
Attempt to send data to the configured HTTP South service endpoints.
Observe the response and error logs.
Expected Behavior:
The data should be successfully sent to all configured HTTP South service endpoints without any errors.
Actual Behavior:
Data is published to the first endpoint, but the others return a 404 error, indicating that the endpoints are not found.
Environment:
Fledge Version: v2.6.0
Plugin: HTTP South
Configuration: Sending data to multiple HTTP South service endpoints on the same port.
The text was updated successfully, but these errors were encountered:
I am using Fledge v2.6.0 with the HTTP South services and trying to send data to multiple HTTP South service endpoints using the same port. However, the data is not being published to the other HTTP South services, and encountering a 404 error.
Steps to Reproduce:
Set up Fledge v2.6.0 and configure the HTTP South plugin to send data to multiple endpoints using the same port.
Attempt to send data to the configured HTTP South service endpoints.
Observe the response and error logs.
Expected Behavior:
The data should be successfully sent to all configured HTTP South service endpoints without any errors.
Actual Behavior:
Data is published to the first endpoint, but the others return a 404 error, indicating that the endpoints are not found.
Environment:
Fledge Version: v2.6.0
Plugin: HTTP South
Configuration: Sending data to multiple HTTP South service endpoints on the same port.
The text was updated successfully, but these errors were encountered: