rsuplido

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

  • Last visited

 Content Type 

Posts posted by rsuplido

    [Support] binhex - PrivoxyVPN

    in Docker Containers

    Posted

    5 minutes ago, binhex said:

    in a word, no, however if you are using a mainstream vpn provider then they typically have multiple servers for each hostname endpoint, and in this case i have coded it such that it will resolve all server ip's and then randomly re-connect on vpn tunnel drop, if you are using a single ip address for the remote line then that will always bite you sooner or later.

    I use NordVPN and they have one .ovpn for each of their 5220 servers in 59 countries. See all of them here for example: https://nordvpn.com/ovpn/

    Thanks.

    [Support] binhex - PrivoxyVPN

    in Docker Containers

    Posted

    Thanks for this! I was wondering if this would support multiple .ovpn files in the openvpn folder -- and maybe use a random one whenever it connects / timesout? I experienced a server going down and it won't connect until I uploaded another .ovpn file, and I only figured that out after a few days.

    <Support> Kru-x - Wekan and MongoDB-wekan templates

    in Docker Containers

    Posted

    On 7/25/2019 at 5:18 PM, normtodd said:

    fwiw i was able to finally the docker started by making a change to MONGO_URL variable in the wekan docker.

     

    i should note that the --link mongodb:db which was populated in extra arguments (and was there on the docker update last night) has been removed completely.

     

    HOWEVER IN MAKING THIS CHANGE IT CREATED A NEW DATABASE AND I LOST ALL PREVIOUS WORK

     

    it may still be somewhere in mongo, but i dont know mongo like i know mysql, so who knows.

     

    my dockers are set up in such as way so as they do not all share a proxynet, but instead have their own IP addresses.  for example mongodb docker is on 10.720.140

     

    to make the wekan docker start, i changed the MONGO_URL to be:

      

    
mongodb://10.72.0.140:27017/db

    instead of the previous MONGO_URL of 

    
mongodb://db

    I realize this change was not advisable as per one of the messages above, but this was the only way i could get it all to start.

     

    i am almost positive this is not the correct way to do it, but this way it starts and the log files are all nominal

     

    I bet your old db/data are still there. On  your case, try changing to: mongodb://10.72.0.140:27017/admin