Hosts file probably does not work for domain names that have dot

Or, set some subdomain pointing to your Wekan server IP address

For some website to be visible at Internet, usually it needs ports 80 and 443 open to Internet

Also, if you have subdomain that points to your private IP address like 192.168.0.100 , it does work inside your local network for all devices, but not at Internet, because private LAN IP addresses are not routed to Internet

BTW, for programmers: There is currently in progress Meteor.js Impact free online conference https://impact.meteor.com , some talks are now in progress, and all of the conference talks are recorded

There are talks about scaling Meteor, PWAs, etc etc

Thanks again for the pointers.

Hello, How can I transfer my Wekan docker-db? I transer "volumes:

  - ./wekan-db:/data/db" but if I start docker-compose it's didn't start (eternal restarting docker-db) 

how can I migrate Wekan-db if I have only "./wekan-db:/data/db" from my other server

@dmitrii See https://github.com/wekan/wekan/wiki/Export-from-Wekan-Sandstorm-grain-.zip-file and https://github.com/wekan/wekan/wiki/Backup

You copy raw MongoDB files to same version of MongoDB database server raw file directory, start MongoDB, do mongodump, restore to Wekan Snap or Wekan Docker

thanks for reply, I have broken docker container with wekan I can't start any docker services on my old VM so can I just transfer my wekan-db directory? because I can't start wekan-db docker and do backup. Have you any advise?

Yes, you just copy your wekan-db directory with those raw mongodb database files to another computer where you have working mongodb of same version

you replace those mongodb files on when mongodb is not running

and then start mongodb

and then try mongodump

can't start wekan-mongo-db container if I replace all mongodb files

if I replaced mongodb files it trigered to infinoty restarting wekan db container

but if I delete / clear back mongo-db directory it's works fine again

Does it give any errors? docker logs wekan-db

sent you a huge log in private message, check please

It seems there is checksum errors, so most likely that data is corrupted

I would recommend restoring from your previous backup. If you really need some data from those files, you could look at them with hex editor, or linux command "strings somefilename"

can't open wekan mongo-db container it's always restarting / droped