search

openmeetings / openmeetings-docker

Docker image for OM
Apache License 2.0
110 stars 56 forks source link

Started normally but inaccessible #32

Open myCodingTrip opened 3 years ago

myCodingTrip commented 3 years ago

Dingtalk_20210706093314 Dingtalk_20210706093242

solomax commented 3 years ago

Hello @myCodingTrip,

I can't see the startup messages in your log could you share your command line?

I have just tried with docker run -i --rm --network host apache/openmeetings:6.0.0 The output was similar to yours, OM was accessible at https://localhost:5443/openmeetings

To check what is wrong you can enter VM as described here: https://github.com/openmeetings/openmeetings-docker "to join running machine" section and check full log at /opt/openmeetings/logs/openmeetings.log

kakiser56 commented 3 years ago

I am having the same issue. Everything starts normally, I can see where openmeetings is deployed, however accessing https://localhost:5443/openmeetings yields HTTP Error 404. The requested resource is not found. I went into the container and looked at the openmeetings.log, but no errors where there. I am running on a Windows 10 box, but that shouldn't matter with Docker I assume.

Kabbu64 commented 2 years ago

I had the same Issue. Seems like your browser does not know where to send your request. I fixed this by going into the container and checked, if mysql was running properly. Go into your container with docker exec -it <container-id or name> bash and run service mysql status. My mysql daemon wasn't running properly, respectively the container didn't know which database to use. Worked for me, maybe it helps you as well.