-
Notifications
You must be signed in to change notification settings - Fork 302
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
SSL support for Swoole HTTP Server not working #155
Comments
You can use the |
Im talking about this flag SWOOLE_SSL where do you see that in the options? |
@viezel feel free to open a PR. However, I think this flag is only available in some Swoole builds not all. You'll need to check with the Swoole team first.
|
Correct, if you do not enable openssl then it will not work |
This however opens a discussion on which swoole modules that is required enabled by Octane. pecl install --configureoptions 'enable-sockets="no" enable-openssl="yes" enable-http2="yes" enable-mysqlnd="yes" enable-swoole-json="no" enable-swoole-curl="yes"' swoole |
Then why it was merged in #342?
It was release yesterday as a patch release (https://github.com/laravel/octane/releases/tag/v1.0.9) but for me it's a breaking change. |
@L3o-pold I also had this issue using Sail, I had to update Sail, replace my published dockerfile, and |
You need to compile Swoole with openssl enabled ( |
if The quick fix without rebuild, define
I think it is better to update to latest Laravel Sail version as it is not using PECL to install Swoole. |
@kiddtang editing And for my case it was not an issue in dev environment with sail but with a production environment that was not having openssl enabled for Swoole. In addition using functional testing (https://laravel.com/docs/8.x/http-tests#making-requests) will not help you to trigger the issue as it's not testing octane unfortunately. |
@L3o-pold I'm getting a similar issue I believe. I'm using Apache vhosts and have generated a let's encryps ssl certificate. How can I serve my application through ssl? I added
to my config file. Do I need to? Or should it be completely done via apache because that gives me a connection refused:
|
Description:
When using Swoole HTTP Server directly without nginx as proxy - then we need to configure SSL.
In Swoole it looks like this:
However, we cannot add the
SWOOLE_SSL
to the Server arguments in here: https://github.com/laravel/octane/blob/master/bin/createSwooleServer.php#L10Can we please expose this as a config?
The text was updated successfully, but these errors were encountered: