The port you have configured to forward via windscribe. The location to connect to, which must be on 'windscribe location' listĪllow other applications on the docker bridge to connect to this container if onĮnable the windscribe firewall if on, which is recommended. The port to connect to windscribe over, which must be on 'windscribe port' list for that protocol The protocol to use when connecting to windscribe, which must be on 'windscribe protocol' list The password associated with the username The username used to connect to windscribe The numeric group ID to run the application as, and assign to the group docker_group The nummeric user ID to run the application as, and assign to the user docker_user dockerĬontainer images are configured using parameters passed at runtime (such as those above). Here are some example snippets to help you get started creating a container. People that follow the guide and don't look into it aren't going to have it configured correctly then. I did check 'proxy / anonymizer' in my custom OpenDNS custom filter list, but windscribe seems to function perfectly 'you are connected now'. If you configured it correctly, your router will use our DNS server (the VPN node itself) while connected. For comprehensive privacy protection, use our desktop and browser combo (theyre both free). But a very easy way for a kid to bypass parental control with OpenDNS is to install a vpn extension to chrome for example, such as windscribe. It is called after the health check for the VPN is completed successfully. You can use any DNS provider, as it's only used while VPN is disconnected to resolve the hostname in the OpenVPN config. It MUST return 0 if the container is healthy. This script will be run periodically to check the health of the container. This script should never exit, and will be run as docker_user:docker_group, with the UID and GID specified in PUID and GUID. This script is designed to start the user application after the connection to the VPN has been established. It is run as root, and should be used to prepare the environment for the running app. This script is designed to set up the environment for the running application. There are three script files placed in the /opt/scripts directory that are designed to be overwritten: This documentation format is inspired by the great people over at linuxserver.io. It just handles connecting to windscribe for the moment, and making sure the connection remains active and secure. Added support for native aarch64 (arm64) Ubuntu build. Added icon on connect screen indicating if connection is auto, manual, or network preferred protocol. Added custom alert screens, replacing the native OS message boxes. It contains health-checking, and a framework for extending the image however you like to serve your own purposes. Added support for DNS-over-HTTPS (DoH) and split DNS to the Connected DNS feature. It does not forward any ports, has onely one volume for the docker_user, and exits immediately by default. DNS and IP level blocker that can be used against malware, ads+trackers, social networks, porn, gambling, fake. Windscribe docker container, as a base for other images. Windscribe VPN: The Good, the Bad and the.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |