Skip to content
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

element-we stopped working after latest update #29009

Closed
jinks opened this issue Jan 16, 2025 · 2 comments
Closed

element-we stopped working after latest update #29009

jinks opened this issue Jan 16, 2025 · 2 comments
Labels
A-Developer-Experience O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect

Comments

@jinks
Copy link

jinks commented Jan 16, 2025

Steps to reproduce

  1. Where are you starting? What can you see?

I'm running element-web from a unprivileged podman container. as of 2025-01-15 this stopped working

Outcome

with the following error messages:

Jan 16 08:59:10 themis systemd-element[2687339]: 2025/01/16 08:59:10 [warn] 1#1: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
Jan 16 08:59:10 themis systemd-element[2687339]: nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /etc/nginx/nginx.conf:2
Jan 16 08:59:10 themis systemd-element[2687339]: 2025/01/16 08:59:10 [emerg] 1#1: bind() to 0.0.0.0:80 failed (13: Permission denied)
Jan 16 08:59:10 themis systemd-element[2687339]: nginx: [emerg] bind() to 0.0.0.0:80 failed (13: Permission denied)

Based on nginx-unprivileged documentation I set the env var NGINX_PORT to a high port but this did not solve the issue.

Operating system

Linux

Browser information

N/A

URL for webapp

private server, version docker:latest

Application version

N/A

Homeserver

No response

Will you send logs?

No

@jinks jinks added the T-Defect label Jan 16, 2025
@dosubot dosubot bot added A-Developer-Experience O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Minor Impairs non-critical functionality or suitable workarounds exist S-Major Severely degrades major functionality or product features, with no satisfactory workaround labels Jan 16, 2025
@t3chguy
Copy link
Member

t3chguy commented Jan 16, 2025

Based on nginx-unprivileged documentation I set the env var NGINX_PORT to a high port but this did not solve the issue.

You're following the wrong docs:

The behaviour of the docker image can be customised via the following
environment variables:
- `ELEMENT_WEB_PORT`
The port to listen on (within the docker container) for HTTP
traffic. Defaults to `80`.

@t3chguy t3chguy closed this as completed Jan 16, 2025
@t3chguy t3chguy closed this as not planned Won't fix, can't repro, duplicate, stale Jan 16, 2025
@jinks
Copy link
Author

jinks commented Jan 16, 2025

AHA! That explains it. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Developer-Experience O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Major Severely degrades major functionality or product features, with no satisfactory workaround S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect
Projects
None yet
Development

No branches or pull requests

2 participants