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

Nginx failing to start for non ipv6 setup #1889

Closed
wastlmuc opened this issue Sep 19, 2022 · 4 comments · Fixed by #2254
Closed

Nginx failing to start for non ipv6 setup #1889

wastlmuc opened this issue Sep 19, 2022 · 4 comments · Fixed by #2254
Assignees
Labels
bug future3 Relates to future3 development

Comments

@wastlmuc
Copy link

Describe your problem

Nginx service fails to start with nginx: [emerg] socket() [::]:80 failed

What's your hardware set up?

RPi veversion 1

Solution

In /etc/nginx/sites-enabled/default comment out listen [::]:80 default_server; .
If this is the desired way, I can adapt the installation script for this.

@wastlmuc wastlmuc added bug future3 Relates to future3 development needs triage labels Sep 19, 2022
@s-martin
Copy link
Collaborator

Hi, thanks for your suggestion.
Can you add a pull request with the necessary change?

@s-martin
Copy link
Collaborator

3.4 was just released, https://github.com/MiczFlor/RPi-Jukebox-RFID/releases/tag/v3.4.0

Could you check, if your problem was fixed?

@AlvinSchiller
Copy link
Collaborator

Will be fixed shortly in 3.5.1

@AlvinSchiller AlvinSchiller self-assigned this Feb 11, 2024
@AlvinSchiller AlvinSchiller linked a pull request Feb 11, 2024 that will close this issue
@pabera pabera mentioned this issue Feb 11, 2024
9 tasks
@AlvinSchiller
Copy link
Collaborator

fixed with #2254

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug future3 Relates to future3 development
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants