JOSEPH ENGELMANN

Members
  • Posts

    4
  • Joined

  • Last visited

Posts posted by JOSEPH ENGELMANN

  1. On 10/20/2022 at 6:55 PM, Vault 687 said:

    I was having the same issue. This is what I did to fix it.

     

    1. Created minio share /mnt/user/minio

    2. Started minio and let it create /.minio.sys/config

    3. Stopped minio

    4. Created config.json in config folder

    5. Pasted this config file into it: https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/cheesemarathon/minio.xml

    6. Started again

     

    Works for me now. Hope this helps someone else.

    This method worked for me as well! thank you.

    • Like 1
  2. has anyone gotten this to work with a dedicated ip assigned by the vpn provider? i have gone over the provider's doc's and the vpn.md for docker container but for some reason i have no idea why it won't use the dedicated ip, i have tried to change the  "remote" domain "ca-toronto.privacy.network 1197" for example to the ip i was assigned, still have the auth-user-pass.conf in there and it fails to connect and therefore also doesn't finish the startup for the container when the ip is used. here is the the main part of the config file if anyone has any idea how to specify how the container connects and to what ip, that would be great.

    client
    dev tun
    proto udp
    remote ca-toronto.privacy.network 1197 "Tried to change this to the ip of the dedicated ip i was assigned without success"
    resolv-retry infinite
    nobind
    persist-key
    persist-tun
    cipher aes-256-cbc
    auth sha256
    tls-client
    remote-cert-tls server
    
    auth-user-pass
    compress
    verb 1
    reneg-sec 0