-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Great image #6
Comments
Hello!
No, I start it over http only.
чт, 6 сент. 2018 г., 22:20 sdvroot <notifications@github.com>:
… @nikosch86 <https://github.com/nikosch86> Hello, thx for great job,
Did you try to start it on https ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFk8NbQlo5hTJ1Cph3cpni6s_bcCbXGgks5uYT0egaJpZM4WdKgj>
.
|
Пробую поднять на https Пока говорит |
Есть репозиторий с настройками?
чт, 6 сент. 2018 г., 22:38 sdvroot <notifications@github.com>:
… Пробую поднять на https
Поменял порт в docker-compose.yml c 80 на 443
Прокинул в сертификат в контейнер через - Volume
В nginx.conf добавил путь к сертификату, сказал слушать 443 порт, может
подскажите что еще нужно чтоб работало?
Пока говорит
An error occurred during a connection to ip address. SSL received a record
that exceeded the maximum permissible length. Error code:
SSL_ERROR_RX_RECORD_TOO_LONG
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFk8NX7MSH24PxlobxBqlC7KcwouxvgIks5uYUGMgaJpZM4WdKgj>
.
|
Не, нету, закинул на почту docker-compose.yml и nginx.conf |
чт, 6 сент. 2018 г. в 18:44, mdenissov <notifications@github.com>:
… Есть репозиторий с настройками?
чт, 6 сент. 2018 г., 22:38 sdvroot ***@***.***>:
> Пробую поднять на https
> Поменял порт в docker-compose.yml c 80 на 443
> Прокинул в сертификат в контейнер через - Volume
> В nginx.conf добавил путь к сертификату, сказал слушать 443 порт, может
> подскажите что еще нужно чтоб работало?
>
> Пока говорит
> An error occurred during a connection to ip address. SSL received a
record
> that exceeded the maximum permissible length. Error code:
> SSL_ERROR_RX_RECORD_TOO_LONG
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#6 (comment)>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AFk8NX7MSH24PxlobxBqlC7KcwouxvgIks5uYUGMgaJpZM4WdKgj>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AkemV4GozX4HnVyI03ykl7WNL1lcOeK3ks5uYULOgaJpZM4WdKgj>
.
|
Добрый день, Можешь попробовать запустить с SSL ? у меня вышло запустить https://ip address/auth/mock/ после логина пустой экран https://ip address |
enabling SSL should be a matter of configuring the Reverse Proxy and the URLs (in the Environment Variables for the services) |
Hi, @nikosch86 thx for response, I will be grateful for help My configs version: '2' volumes: services: nginx.conf worker_processes auto; events { http { default_type application/octet-stream; upstream stf_app { upstream stf_auth { upstream stf_storage_apk { upstream stf_storage_image { upstream stf_storage { upstream stf_websocket { upstream stf_api { types { map $http_upgrade $connection_upgrade { server {
} Do I have to change the settings somewhere else?) |
It's a little hard to read because of the formatting, switching in and out of code view. In your config it looks like nginx is only listening on port 443, try listening on both, 80 and 443. |
configurations.txt Yeah connection still secure after enter credentials docker-compose logs: |
@mdenissov , @nikosch86 Guys, where are you? need yours help :) |
As expected, it just works, not sure what your problem is, it is also very hard to see what you changed and what the output is.
|
closing due to inactivity |
@nikosch86 Hello, thx for great job,
Did you try to start it on https ?
The text was updated successfully, but these errors were encountered: