Enabling ssl for the compliance servers' external server (port 8003)?

[bonen]

When I run the compliance server with the below configs I get the below error:

[bridge.cfg]

port = 8006
horizon = "https://horizon-testnet.stellar.org"
network_passphrase = "Test SDF Network ; September 2015"
compliance = "http://localhost:8004"
...

[stellar.toml]

FEDERATION_SERVER = "https://domain:8002/federation"
AUTH_SERVER = "https://domain:8003"
...

ERROR

INFO[0000] Starting external server on :8003
INFO[0000] Starting internal server on :8004
ERRO[0004] Error sending request to auth server auth_server="https:/domain:8003" err="Post https://domain:8003: http: server gave HTTP response to HTTPS client"

It can be fixed by replacing https with http in [stellar.toml]

FEDERATION_SERVER = "https://domain:8002/federation"
AUTH_SERVER = "http://domain:8003"
...

I think that shouldn't be the behaviour we want right? Can it be the case that the compliance server erroneously doesn't activate ssl for the external server?

Also, in the documentation it says that within [bridge.cfg] the compliance variable should be set to https://domain:8004 (instead of http://localhost) but if I actually do that I get the error:

ERRO[0014] Error sending request to compliance server err="Post https://domain:8004/send: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"

PS
The documentation mentions config_compliance.toml & config_bridge.toml & port 8001 instead of compliance.cfg & bridge.cfg & port 8006 on the page:
https://www.stellar.org/developers/guides/anchor/4-compliance-server.html

[antb123]

We are using nginx as a proxy which maybe should be the recommended setup as it makes ssl setup super easy with letsencrypt.org

…

On 1 March 2018 at 23:26, Koen ***@***.***> wrote: When I run the compliance server with the below configs I get the below error: [bridge.cfg] port = 8006 horizon = "https://horizon-testnet.stellar.org" network_passphrase = "Test SDF Network ; September 2015" compliance = "http://localhost:8004" ... [stellar.toml] FEDERATION_SERVER = "https://domain:8002/federation" AUTH_SERVER = "https://domain:8003" ... ERROR INFO[0000] Starting external server on :8003 INFO[0000] Starting internal server on :8004 ERRO[0004] Error sending request to auth server auth_server="https:/domain:8003" err="Post https://domain:8003: http: server gave HTTP response to HTTPS client" It can be fixed by replacing https with http in [stellar.toml] FEDERATION_SERVER = "https://domain:8002/federation" AUTH_SERVER = "http://domain:8003" ... I think that shouldn't be the behaviour we want right? Can it be the case that the compliance server erroneously doesn't activate ssl for the external server? Also, in the documentation it says that within [bridge.cfg] the compliance variable should be set to https://domain:8004 (instead of http://localhost) but if I actually do that I get the error: ERRO[0014] Error sending request to compliance server err="Post https://domain:8004/send: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)" PS The documentation mentions config_compliance.toml & config_bridge.toml & port 8001 instead of compliance.cfg & bridge.cfg & port 8006 on the page: https://www.stellar.org/developers/guides/anchor/4-compliance-server.html — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#102>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQZFzuDKoucJKWRCUyMGgY18v4c0Uw--ks5taAUZgaJpZM4SYY6G> .

-- Anthony BARKER | CTO / dg TEMPO FRANCE <https://tempo.eu.com> | SKYPE: anthony_barker <https://is.gd/ENomHq> | T: +33144839428 <https://is.gd/J9GX3p> | MFR: +33783596325 STATION F, PARIS | WECHAT:ANTB123 | TELEGRAM <https://telegram.me/antb123> | T <http://TWITTER.COM/ANTHONY_BARKER> | L <https://www.linkedin.com/company/tempo-france-sas> | f <https://www.facebook.com/TEMPOMoneyTransfer>

[phra]

offloading ssl with nginx will be the best solution.