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 error installing SOMA #98

Open
jharris-spoonflower-com opened this issue May 19, 2022 · 1 comment
Open

Nginx error installing SOMA #98

jharris-spoonflower-com opened this issue May 19, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@jharris-spoonflower-com

First off, Thank you so much for putting this together. If I can get this last part working with the SOMA add-on, I can see this as a huge help for me.

When installing SOMA, at the end I get the following error:

TASK [monitor-output : Copy nginx config] ***********************************************************************************************
fatal: [localhost]: FAILED! => {"changed": false, "checksum": "d6fe9bae6d78b0dddcc9c13ea5e1b3a90c0ab07b", "msg": "Destination directory /etc/nginx/sites-enabled does not exist"}

My Screenly OSE version does not have /etc/nginx because it is baked into the docker container. I am trying to figure out how to connect to and add the file soma_monout.conf to the containers nginx config, but I have not yet figured out how to do that. If I figure it out before you get back to me, I will post what I did. Thanks again!!

  • Screenly OSE Monitoring Version: 4.3
  • Screenly OSE Version: master@97a0abd
  • Raspbian Version: buster (Pi3B+)
  • Browser Name and version: Firefox 100.0
  • Operating System and version (desktop or mobile): MacOS Big Sur
@didiatworkz
Copy link
Owner

Hello @jharris-spoonflower-com,

the current release of ScreenlyOSE causes the problem.
As soon as Screenly OSE is operated via the Docker container, port 80 is blocked.
Unfortunately, the nginx installation also needs port 80 here, otherwise it cannot be completed successfully.
Therefore, this is currently going wrong.

I will have to rebuild the add-ons so that they only run via Python and no longer need nginx.
But that takes time.

Best
didiatworkz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants