Closed gojennie closed 5 years ago
Try running mongoDB as a separate container. Then run wiki.js. In some instances, the mongo container isn't ready to serve requests by the time wiki.js is booting.
Hi, thank you for replying. I'm puling my hair out at this point. MongoDB is running in a separate container from the start.. It's really strange, now I see the favicon showing up on the corner. And an 502 error.
I'm new to this porting rule so I'm not sure if I understand this correctly. Please help me check my logic.
I finally got it working. It was an issue with reverse proxy and firewall. I hope no one spends as much time as I did so I'll post my solution in case anyone runs into the same troubles.
config.yml:
Note: Ensure that the host is the public domain you will enter to visit the website. This must match otherwise your gonna get an ugly wiki without any CSS.
docker-compose.yml:
Reverse Proxy (inside Synology NAS):
Disable firewall (inside Synology NAS):
Router Configuration (inside Synology NAS):
My understanding corrected from previous post:
I'm so thrilled that it's working after 7 days of hard work... Now I'm going to try installing beta and see which I like better 😄
Hello! This is a help request. I can't seem to get my domain to point to the right place. Any insight would be truly valued~
Problem: When I type my domain in to my browser, the connection hangs. I get this error : ERR_CONNECTION_TIMED_OUT
I am running the Wiki.js V1 and mongodb in a container using docker. They are being hosted on my Synology NAS at home (unfortunately I can't test this at home at the moment). Both containers seem to be working:
Log of Wiki:
Log of DB:
This is the Reverse Proxy Rules:
For your reference, here is the docker-compose.yml file:
And here is the config.yml:
Where did I go wrong? @NGPixel Please help when you get a chance thank you!