Issue with using ingress rules to allow websocket connections

Hey, I’m starting out using Cloudflare, hopefully using the right category here, and I’m trying to figure out how to get a websocket connection going on a tunnel. Wasn’t able to do anything on the dashboard, so I moved over to using the CLI. For some odd reason, it’s giving me a “bad gateway” error every time I try to connect.

Here’s my config file:

tunnel: 48e69d8c-07e3-40f1-9936-e824c19b66a7
credentials-file: C:/Users/Emera/.cloudflared/48e69d8c-07e3-40f1-9936-e824c19b66a7.json

ingress:
  - hostname: testing.emeraldimpulse.com
    service: wss://localhost:8080
  - service: http_status:404

And here’s a copy-pasted log of my command prompt:

C:\Users\Emera>cloudflared tunnel run "Main Desktop"
2022-05-09T01:22:06Z INF Starting tunnel tunnelID=48e69d8c-07e3-40f1-9936-e824c19b66a7
2022-05-09T01:22:06Z INF Version 2022.5.0
2022-05-09T01:22:06Z INF GOOS: windows, GOVersion: go1.17.5, GoArch: amd64
2022-05-09T01:22:06Z INF Settings: map[cred-file:C:/Users/Emera/.cloudflared/48e69d8c-07e3-40f1-9936-e824c19b66a7.json credentials-file:C:/Users/Emera/.cloudflared/48e69d8c-07e3-40f1-9936-e824c19b66a7.json]
2022-05-09T01:22:06Z INF cloudflared will not automatically update on Windows systems.
2022-05-09T01:22:06Z INF Generated Connector ID: e6d4a8a2-2bf2-4a9d-829d-adde3ce1afa2
2022-05-09T01:22:06Z INF Initial protocol http2
2022-05-09T01:22:06Z INF cloudflared does not support loading the system root certificate pool on Windows. Please use --origin-ca-pool <PATH> to specify the path to the certificate pool
2022-05-09T01:22:06Z INF Starting metrics server on 127.0.0.1:63830/metrics
2022-05-09T01:22:08Z INF Connection 4785387e-ed31-4fce-a4f4-42c1c6170664 registered connIndex=0 location=ORD
2022-05-09T01:22:12Z INF Connection e3d5a7a3-c634-45aa-b273-ba95dbf272dd registered connIndex=1 location=DFW
2022-05-09T01:22:12Z INF Connection 09aca76f-39e3-457e-82af-c17d412bcaa9 registered connIndex=2 location=ORD
2022-05-09T01:22:12Z INF Connection 3cef734d-c5d5-43fa-965d-9297ac9c6644 registered connIndex=3 location=DFW
2022-05-09T01:26:24Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: dial tcp [::1]:8080: connectex: No connection could be made because the target machine actively refused it." cfRay=7086a5832f0e93fd-DFW ingressRule=0 originService=wss://localhost:8080
2022-05-09T01:28:28Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: first record does not look like a TLS handshake" cfRay=7086a896fecb677b-DFW ingressRule=0 originService=wss://localhost:8080
2022-05-09T01:28:54Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: first record does not look like a TLS handshake" cfRay=7086a93e28169401-DFW ingressRule=0 originService=wss://localhost:8080
2022-05-09T01:29:19Z ERR  error="Unable to reach the origin service. The service may be down or it may not be responding to traffic from cloudflared: tls: first record does not look like a TLS handshake" cfRay=7086a9da7b29aa33-DFW ingressRule=0 originService=wss://localhost:8080