edgurgel/poxa

trying to run poxa using ssl

Closed this issue · 9 comments

AnkitRathore175 commented

Hi
I m trying to configure the poxa using ssl for wss connection using below configuration in docker
but unable to connect with wss or https however ws/http working fine
FYI, ssl is configured correctly using Let’s Encrypt and all the relavant files are in priv/ssl folder

version: '3'
services:
  dev:
    image: edgurgel/poxa
    container_name: dev
    environment:
      - PORT=8080
      - POXA_APP_KEY=app_key
      - POXA_SECRET=app_secret
      - POXA_APP_ID=1234
      - POXA_SSL=true
      - SSL_PORT=8443
      - SSL_CACERTFILE=ca.cer
      - SSL_CERTFILE=ssl.cer
      - SSL_KEYFILE=ssl.key
    volumes:
      - ../ssl:/priv/ssl
    ports:
      - "8080:8080"
      - "8443:8443"
toannguyen1412 commented

yes. same problem

edgurgel commented

I think I found the problem. I will see if I can release a new version before the end of the year. Thanks for the report

  • ❤️1
toannguyen1412 commented

It work find 8080.
but 8043 not working

edgurgel commented

I couldn't replicate the issue :(

Using my own certificate works fine with curl for example

Revyn112 commented

@edgurgel is this problem fixed? we also can't use wss connections. On Connection the Server closed immediately the connection without log to poxa.
(failed: Error in connection establishment: net::ERR_CONNECTION_CLOSED)
This is something that 100 percent worked some time ago, but with latest version it doesnt. Would be very nice if you look into this problem, our whole app based on this and its critical.

edgurgel commented

I would advise people to use a load balancer with HTTPS support to serve SSL on top of the Poxa HTTP port if they are experiencing these issues. I can't replicate the issue.

Revyn112 commented

@edgurgel i could provide you an access to our system if you want to have a look on it?

edgurgel commented

@Revyn112, I appreciate the offer but ideally some way to replicate so that I can tweak and do whatever is needed to debug.

Maybe a repo that reproduces the issue?

Revyn112 commented

@edgurgel i've fixed this problem after reinstall the whole system - don't know exactly what the problem was but now it works all like a charm like before ;) keep the good work up