uWSGI https server with systemd socket activation
I run a https web server, using uWSGI (version 2.0.14-debian; on a raspberry Pi with raspian / debian 9 stretch).
For https, I have the following lines in configuration file:
[uwsgi]
...
protocol = https
https-socket = =0,/etc/ssl/certs/star.chained-certificate.crt,/etc/ssl/private/star.privatekey.pem
...
I provide the port as "--shared-socket 0.0.0.0:443" in my systemd service file. This works as long as I start the uwsgi server as systemd service, but not when socket-activated.
To use socket-activation, I do not specify the shared-socket in the uwsgi.service file. While an incoming request starts the service, no data or request is received by uwsgi and the https request times out.
Looking at the source code (uwsgi_setup_systemd() and uwsgi_bind_sockets()), the socket provided by systemd might be bound as "--socket" and not as "--shared-socket" (which would explain why socket activation works in my hands for http but not for https).
What is the correct way to set-up uWSGI for https and socket-activation?
linux https systemd uwsgi
asked Dec 29 '18 at 15:59
Al_Al_
111
add a comment |
I run a https web server, using uWSGI (version 2.0.14-debian; on a raspberry Pi with raspian / debian 9 stretch).
For https, I have the following lines in configuration file:
[uwsgi]
...
protocol = https
https-socket = =0,/etc/ssl/certs/star.chained-certificate.crt,/etc/ssl/private/star.privatekey.pem
...
I provide the port as "--shared-socket 0.0.0.0:443" in my systemd service file. This works as long as I start the uwsgi server as systemd service, but not when socket-activated.
To use socket-activation, I do not specify the shared-socket in the uwsgi.service file. While an incoming request starts the service, no data or request is received by uwsgi and the https request times out.
Looking at the source code (uwsgi_setup_systemd() and uwsgi_bind_sockets()), the socket provided by systemd might be bound as "--socket" and not as "--shared-socket" (which would explain why socket activation works in my hands for http but not for https).
What is the correct way to set-up uWSGI for https and socket-activation?
linux https systemd uwsgi
asked Dec 29 '18 at 15:59
Al_Al_
111
add a comment |
I run a https web server, using uWSGI (version 2.0.14-debian; on a raspberry Pi with raspian / debian 9 stretch).
For https, I have the following lines in configuration file:
[uwsgi]
...
protocol = https
https-socket = =0,/etc/ssl/certs/star.chained-certificate.crt,/etc/ssl/private/star.privatekey.pem
...
I provide the port as "--shared-socket 0.0.0.0:443" in my systemd service file. This works as long as I start the uwsgi server as systemd service, but not when socket-activated.
To use socket-activation, I do not specify the shared-socket in the uwsgi.service file. While an incoming request starts the service, no data or request is received by uwsgi and the https request times out.
Looking at the source code (uwsgi_setup_systemd() and uwsgi_bind_sockets()), the socket provided by systemd might be bound as "--socket" and not as "--shared-socket" (which would explain why socket activation works in my hands for http but not for https).
What is the correct way to set-up uWSGI for https and socket-activation?
linux https systemd uwsgi
asked Dec 29 '18 at 15:59
Al_Al_
111
I run a https web server, using uWSGI (version 2.0.14-debian; on a raspberry Pi with raspian / debian 9 stretch).
For https, I have the following lines in configuration file:
[uwsgi]
...
protocol = https
https-socket = =0,/etc/ssl/certs/star.chained-certificate.crt,/etc/ssl/private/star.privatekey.pem
...
I provide the port as "--shared-socket 0.0.0.0:443" in my systemd service file. This works as long as I start the uwsgi server as systemd service, but not when socket-activated.
To use socket-activation, I do not specify the shared-socket in the uwsgi.service file. While an incoming request starts the service, no data or request is received by uwsgi and the https request times out.
Looking at the source code (uwsgi_setup_systemd() and uwsgi_bind_sockets()), the socket provided by systemd might be bound as "--socket" and not as "--shared-socket" (which would explain why socket activation works in my hands for http but not for https).
What is the correct way to set-up uWSGI for https and socket-activation?
linux https systemd uwsgi
linux https systemd uwsgi
asked Dec 29 '18 at 15:59
Al_Al_
111
asked Dec 29 '18 at 15:59
Al_Al_
111
asked Dec 29 '18 at 15:59
Al_Al_
111
asked Dec 29 '18 at 15:59
Al_Al_
111
asked Dec 29 '18 at 15:59
Al_Al_
111
111
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388766%2fuwsgi-https-server-with-systemd-socket-activation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388766%2fuwsgi-https-server-with-systemd-socket-activation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
