snipe / snipe-it

A free open source IT asset/license management system
https://snipeitapp.com
GNU Affero General Public License v3.0
11.21k stars 3.2k forks source link

Help Request - SSL in docker #7768

Closed gavin-commit closed 4 years ago

gavin-commit commented 4 years ago

Expected Behavior (or desired behavior if a feature request)

Snipe-IT has neen installed on a Ubuntu Server and Docker, with docker companion. Cert files have been imported to /var/lib/snipeit/ssl and names accordingly.

The Docker-compose.yml file has been updated to: APP_URL=https://localhost

and Ports 443:443 added to the ports section.

After restarting the docker we expected the site to be available over ssl.


Actual Behavior

the site was then not avilable over port 80 or 443, and we had to roll back.


Please confirm you have done the following before posting your bug report:


Provide answers to these questions:

Please do not post an issue without answering the related questions above. If you have opened a different issue and already answered these questions, answer them again, once for every ticket. It will be next to impossible for us to help you.

https://snipe-it.readme.io/docs/getting-help

stale[bot] commented 4 years ago

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

stale[bot] commented 4 years ago

This issue has been automatically closed because it has not had recent activity. If you believe this is still an issue, please confirm that this issue is still happening in the most recent version of Snipe-IT and reply to this thread to re-open it.

Iizuki commented 2 years ago

I recently encountered a similar issue. In my case the reason was that the certificate files were owned by root, and therefore the docker user inside the container could not use them. Chowning them to docker fixed the problem.