FoxGate AntiVPN 1.0.9
An advanced AntiVPN for your server, protect your server from VPNs and more FREE! ✨
Page 1
1.0.9
Mar 7, 2025
Version 1.0.9
- ⚠ Fixed users without permissions to the command can see tab-arguments. This can show cached IP's, update now! (If you don't has plugin that hide tab-completion)
- Support now 1.3.x to 1.21.x, changed internal libraries to Gson.
- Improved command and improved performance.
- Now libraries message are hidden by default, enable it with using argument '-Dfoxgate.enableLibrariesLog'.
- Fixed in BungeeCord, player's get invalid packet for commands, making this only working in console only, now works in both.
FoxGate Premium was released! :D
See the description section to view where you can purchase it, you can join to the discord server for any question about it.
1.0.8
Mar 4, 2025
Version 1.0.8 + Announce.
We are happy to announce... FoxGate Premium was released! :D
See the description section to view where you can purchase it, you can join to the discord server for any question about it.
Changelogs:
- Fixed compatibility with some services, like ProxyCheck.
- Improved performance and handling with the database, using totally async for Velocity and BungeeCord.
Configuration
# ___ _ _
# / \__ _| |_ __ _| |__ __ _ ___ ___
# / /\ / _` | __/ _` | '_ \ / _` / __|/ _ \
# / /_// (_| | || (_| | |_) | (_| \__ \ __/
# /___,' \__,_|\__\__,_|_.__/ \__,_|___/\___|
# Configure a database for use.
database:
# - Available options in type.
# All options use HikariCP for better performance.
# |=> MySQL
# |=> MariaDB
# |=> PostgreSQL
# |=> SQLite
# |=> H2
#
# If you change this configuration and your server is already
# started. You can use the command "/foxgate db reconnect" to
# apply the changes without restarting plugin or server.
# Remember first reload the plugin with "/foxgate reload"
# and use that command.
type: "SQLite"
# Edit table in case you want a different.
# If you want to use your actually stats (of 1.0.5-pre4 or older),
# use the next:
# - "vpn_cache"
table: "foxgate"
# MariaDB/MySQL databases type. Edit here.
remote:
# Determine information of your database.
hostname: "localhost"
port: 3306
database: "foxav_db"
username: "root"
password: "password123"
# These settings apply to the MySQL/MariaDB connection pool (HikariCP).
# - Default values are suitable for most users. Only modify these if you know what you're doing!
pool-settings:
# The maximum number of connections in the connection pool.
# - Determines the upper limit of active database connections that can be managed simultaneously.
# - Setting this too high can overload your database server, while setting it too low can cause delays.
# Example:
# If your server has high traffic and the database can handle it, set this to 10 or higher.
# Recommended: 10
# More information: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
maximum-pool-size: 10
# Minimum number of idle connections to maintain in the pool.
# - The pool will try to maintain this number of idle (inactive) connections ready for use.
# - Setting this equal to 'maximum-pool-size' creates a fixed-size connection pool,
# ensuring consistent resource allocation.
# Example:
# For a server with occasional traffic spikes, set this to half of 'maximum-pool-size'.
# Recommended: 2
minimum-idle: 2
# Sets the maximum time an idle connection can remain in the pool before being automatically closed.
# - Connections that remain idle for longer than the configured value will be removed from the pool
# and replaced with new connections as needed.
# - This is useful to free up resources and keep connections "fresh" avoiding possible problems with
# stale connections.
# Recommended: 600000 (10 minutes)
idle-timeout: 600000
# Maximum lifetime of a connection in the pool, in milliseconds.
# - Connections older than this value will be closed and replaced.
# - This prevents stale connections from lingering indefinitely and reduces database timeout issues.
# - Should be at least 30 seconds less than the timeout imposed by the database itself.
# Example:
# If your database timeout is 30 minutes, set this value to 25 minutes (1500000 ms).
# Recommended: 1500000 (25 minutes)
maximum-lifetime: 1500000
# Frequency of pings to keep the connection alive, in milliseconds.
# - This prevents connections from being closed due to inactivity (common in many databases or firewalls).
# - Must be less than 'maximum-lifetime' and greater than 30 seconds (30000 ms).
# Example:
# For long-running servers, a value of 10 minutes (600000 ms) is generally ideal.
# Recommended: 600000 (10 minutes)
keepalive-time: 600000
# The maximum time in milliseconds to wait for a connection from the pool.
# - If no connection is available within this time, an exception will be thrown.
# - Setting a low value ensures responsiveness but may cause issues under heavy load.
# Example:
# For responsive applications, a value between 3-5 seconds (3000-5000 ms) is ideal.
# Recommended: 5000 (5 seconds)
connection-timeout: 5000
# Custom validation timeout (time taken to validate a connection), in milliseconds.
# - Determines how long the pool will wait while testing if a connection is still valid.
# - A low value improves responsiveness, but setting it too low may cause false negatives.
# Example:
# For most databases, 3 seconds (3000 ms) is sufficient for validation.
# Recommended: 3000 (3 seconds)
validation-timeout: 3000
# Leak detection threshold in milliseconds.
# - This setting helps detect connections that are not properly closed.
# - If a connection is checked out but not closed within this time, a warning will be logged.
# - Useful for debugging connection leaks in plugins or applications.
# Example:
# If you expect queries to be fast, a value of 60 seconds (60000 ms) can help catch leaks.
# If you have long transactions, set a higher value to avoid false positives.
# Recommended: 60000 (1 minute)
leak-detection-threshold: 60000
# Custom properties for advanced users.
# Add any additional properties to fine-tune the connection.
#
# You can uncomment unnecesary properties or remove,
# also edit to values that is perfect for you.
# (!) THIS PROPERTIES IS BASED WITH SUPPORT
# MARIADB, IF YOU GET ERROR IN MYSQL, YOU CAN
# ADAPT OR CONSIDERING TO CHANGE TO MARIADB,
# THAT WORKS WITH MYSQL DATABASES.
properties:
# - SSL.
# Database connection settings.
# Adjust these properties to optimize the connection with your MySQL/MariaDB server.
# Enables or disables SSL for secure connections.
# It is highly recommended to set this to true if your server supports SSL.
# Default is false, as many MySQL/MariaDB servers do not support SSL.
sslMode: "disabled"
requireSSL: "false" # If set to "true", forces SSL connections. Overrides 'sslMode'.
verifyServerCertificate: "false" # Validates the server's SSL certificate. Set to "true" for production.
# - Connection Optimization
cachePrepStmts: "true" # Enables prepared statement caching
prepStmtCacheSize: "250" # Number of prepared statements to cache
prepStmtCacheSqlLimit: "2048" # Maximum size of a query in the cache
useServerPrepStmts: "true" # Uses server-side prepared statements
# - Performance and Buffering
rewriteBatchedStatements: "true" # Optimizes batch insert/update performance
useCompression: "false" # Enables compression for data transfer (optional)
maintainTimeStats: "false" # Disables time statistics for improved performance
autoReconnect: "true" # Automatically reconnects if the connection is lost
# - Character Encoding
# Specifies whether Unicode character encoding should be used.
# If working with multilingual data, this is highly recommended.
useUnicode: "true"
# Defines the character encoding for the database connection.
# Use "utf8" for compatibility with most character sets.
characterEncoding: "utf8"
# - Time Zone
serverTimezone: "UTC" # Ensures consistent timezone handling
postgresql:
hostname: "localhost"
port: 5432
database: "foxav_db"
username: "postgres"
password: "password123"
# Database connection settings for PostgreSQL.
settings:
# Adjust these properties to optimize the connection with your PostgreSQL server.
# Enables or disables SSL for secure connections.
# It is highly recommended to set this to true if your server supports SSL.
# Default is false.
ssl: false
# The maximum time in seconds to wait for a connection from the pool.
# Choose a value between 1 and 5 for a balance between availability and performance.
# Recommended: 3.0
connectiontimeout: 3.0
# Specifies whether Unicode character encoding should be used.
# PostgreSQL natively supports Unicode, so this can be left as true.
useUnicode: true
# Defines the character encoding for the database connection.
# Use "UTF-8" to handle multilingual data and ensure compatibility.
characterEncoding: "UTF-8"
# Keeps idle connections alive.
tcpKeepAlive: true
# Timeout for socket operations in seconds.
socketTimeout: 30
# Number of prepared statement executions before switching to server-side prepared statements.
prepareThreshold: 5
# Application name for debugging or monitoring purposes.
applicationName: "FoxGate"
# Enables optimized binary transfer for certain data types.
binaryTransfer: true
# These settings apply to this PostgreSQL, because uses Hikari for connection.
# - Default values are suitable for most users. Only modify these if you know what you're doing!
pool-settings:
# The maximum number of connections in the connection pool.
# - Determines the upper limit of active database connections that can be managed simultaneously.
# - Setting this too high can overload your database server, while setting it too low can cause delays.
# Example:
# If your server has high traffic and the database can handle it, set this to 10 or higher.
# Recommended: 10
# More information: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
maximum-pool-size: 10
# Minimum number of idle connections to maintain in the pool.
# - The pool will try to maintain this number of idle (inactive) connections ready for use.
# - Setting this equal to 'maximum-pool-size' creates a fixed-size connection pool,
# ensuring consistent resource allocation.
# Example:
# For a server with occasional traffic spikes, set this to half of 'maximum-pool-size'.
# Recommended: 2
minimum-idle: 2
# Maximum lifetime of a connection in the pool, in milliseconds.
# - Connections older than this value will be closed and replaced.
# - This prevents stale connections from lingering indefinitely and reduces database timeout issues.
# - Should be at least 30 seconds less than the timeout imposed by the database itself.
# Example:
# If your database timeout is 30 minutes, set this value to 25 minutes (1500000 ms).
# Recommended: 1800000 (30 minutes)
maximum-lifetime: 1800000
# The maximum time in milliseconds to wait for a connection from the pool.
# - If no connection is available within this time, an exception will be thrown.
# - Setting a low value ensures responsiveness but may cause issues under heavy load.
# Example:
# For responsive applications, a value between 30-50 seconds (30000-50000 ms) is ideal.
# Recommended: 30000 (30 seconds)
connection-timeout: 30000
# Leak detection threshold in milliseconds.
# - This setting helps detect connections that are not properly closed.
# - If a connection is checked out but not closed within this time, a warning will be logged.
# - Useful for debugging connection leaks in plugins or applications.
# Example:
# If you expect queries to be fast, a value of 60 seconds (60000 ms) can help catch leaks.
# If you have long transactions, set a higher value to avoid false positives.
# Recommended: 60000 (1 minute)
leak-detection-threshold: 60000
sqlite:
file: "FoxGate.db"
# These settings apply to this SQLite, because uses Hikari for connection.
# - Default values are suitable for most users. Only modify these if you know what you're doing!
#
# Yeah... I know HikariCP isn't better to use with SQLite, but is only for avoid any
# type of errors! Please, don't kill me!
pool-settings:
# The maximum number of connections in the connection pool.
# - Determines the upper limit of active database connections that can be managed simultaneously.
# - Setting this too high can overload your database server, while setting it too low can cause delays.
# Example:
# If your server has high traffic and the database can handle it, set this to 10 or higher.
# Recommended: 10
# More information: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
maximum-pool-size: 10
# Minimum number of idle connections to maintain in the pool.
# - The pool will try to maintain this number of idle (inactive) connections ready for use.
# - Setting this equal to 'maximum-pool-size' creates a fixed-size connection pool,
# ensuring consistent resource allocation.
# Example:
# For a server with occasional traffic spikes, set this to half of 'maximum-pool-size'.
# Recommended: 1
minimum-idle: 1
# Maximum lifetime of a connection in the pool, in milliseconds.
# - Connections older than this value will be closed and replaced.
# - This prevents stale connections from lingering indefinitely and reduces database timeout issues.
# - Should be at least 30 seconds less than the timeout imposed by the database itself.
# Example:
# If your database timeout is 30 minutes, set this value to 25 minutes (1500000 ms).
# Recommended: 1800000 (30 minutes)
maximum-lifetime: 1800000
# The maximum time in milliseconds to wait for a connection from the pool.
# - If no connection is available within this time, an exception will be thrown.
# - Setting a low value ensures responsiveness but may cause issues under heavy load.
# Example:
# For responsive applications, a value between 30-50 seconds (30000-50000 ms) is ideal.
# Recommended: 30000 (30 seconds)
connection-timeout: 30000
# Leak detection threshold in milliseconds.
# - This setting helps detect connections that are not properly closed.
# - If a connection is checked out but not closed within this time, a warning will be logged.
# - Useful for debugging connection leaks in plugins or applications.
# Example:
# If you expect queries to be fast, a value of 60 seconds (60000 ms) can help catch leaks.
# If you have long transactions, set a higher value to avoid false positives.
# Recommended: 60000 (1 minute)
leak-detection-threshold: 60000
h2:
file: "h2db"
# These settings apply to this H2, because uses Hikari for connection.
# - Default values are suitable for most users. Only modify these if you know what you're doing!
pool-settings:
# The maximum number of connections in the connection pool.
# - Determines the upper limit of active database connections that can be managed simultaneously.
# - Setting this too high can overload your database server, while setting it too low can cause delays.
# Example:
# If your server has high traffic and the database can handle it, set this to 10 or higher.
# Recommended: 10
# More information: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
maximum-pool-size: 10
# Minimum number of idle connections to maintain in the pool.
# - The pool will try to maintain this number of idle (inactive) connections ready for use.
# - Setting this equal to 'maximum-pool-size' creates a fixed-size connection pool,
# ensuring consistent resource allocation.
# Example:
# For a server with occasional traffic spikes, set this to half of 'maximum-pool-size'.
# Recommended: 1
minimum-idle: 1
# Maximum lifetime of a connection in the pool, in milliseconds.
# - Connections older than this value will be closed and replaced.
# - This prevents stale connections from lingering indefinitely and reduces database timeout issues.
# - Should be at least 30 seconds less than the timeout imposed by the database itself.
# Example:
# If your database timeout is 30 minutes, set this value to 25 minutes (1500000 ms).
# Recommended: 1800000 (30 minutes)
maximum-lifetime: 1800000
# The maximum time in milliseconds to wait for a connection from the pool.
# - If no connection is available within this time, an exception will be thrown.
# - Setting a low value ensures responsiveness but may cause issues under heavy load.
# Example:
# For responsive applications, a value between 30-50 seconds (30000-50000 ms) is ideal.
# Recommended: 30000 (30 seconds)
connection-timeout: 30000
# Leak detection threshold in milliseconds.
# - This setting helps detect connections that are not properly closed.
# - If a connection is checked out but not closed within this time, a warning will be logged.
# - Useful for debugging connection leaks in plugins or applications.
# Example:
# If you expect queries to be fast, a value of 60 seconds (60000 ms) can help catch leaks.
# If you have long transactions, set a higher value to avoid false positives.
# Recommended: 60000 (1 minute)
leak-detection-threshold: 60000
# When an IP isn't detected a vpn or proxy, this need to save in
# cache to don't make more requests for a little time for save
# performance and requests, customizable here.
bypass:
# Enable this feature?
enable: true
# Determine the amount in hours to save the IP in cache and avoid
# make more requests to this IP. Useful to save performance and
# verify only one time for certain time.
#
# Recommended: 2
# Type 'permanent' for bypass permanent.
expiration_time: 2
# When an IP is detected in a result, this is save in the cache
# to don't make more request for a little time, this value is
# saved in hours.
#
# Recommended: 36
# Type 'permanent' for blocking permanent.
expiration_time: 36- Added new service for detecting Proxy, VPN and Datacenter: IPDetective
# ⛽ IPDetective
# https://ipdetective.io/
#
# Details:
# https://ipdetective.io/login
#
# - 1,000 daily requests, free account.
# - 30k daily requests, basic account.
# - 80k daily requests, premium account.
# - 200k daily requests, enterprise account.
ipdetective:
# Enable this service?
enabled: false
# Model request to use.
model: "JSON"
# Headers in case is necessary.
#
# Set to: 'headers: []' to disable.
headers:
'x-api-key': 'KEY'
# URL.
url: "https://api.ipdetective.io/ip/%IP%?info=true"
# Values to check.
values:
# Fields to check.
fields:
- "type"
# Type to determine.
type: ["vpn", "datacenter", "bot", "proxy"]
1.0.7
Feb 19, 2025
Version 1.0.7
- FIXED VELOCITY SUPPORT, USE THIS VERSION FOR VELOCITY USERS NOW.
- Fixed updater checker returning invalid version.
- Fixed some displays.
We are working for the premium version, this for the moment has the webhook and geo (new, view how this system is in new configuration of this version) system, you can contact in the discord support for purchase with PayPal (for the moment, only). This go to be public for purchase when I finish all the systems planned.
1.0.6
Feb 16, 2025
Version 1.0.6
- Fixed some problems.
- Improved a little more the performance.
- Updated libraries.
- Libraries now relocate to avoid problems with software, like Carbon.
- Fixed permissions problems with Velocity.
- Fixed problems with caching in the database.
- Now the plugin use shaded class for reduce size and better compatibility.
- Improved a little more the system of detection in VPNs.
- Improved compatibility with Minecraft 1.7.x.
- Fixed AntiVPNio endpoint.
We are working for the premium version, this for the moment has the webhook system, you can contact in the discord support for purchase with PayPal (for the moment, only). This go to be public for purchase when I finish all the systems planned.
1.0.5
Jan 21, 2025
Version 1.0.5
Changelogs
- Fixing default value for MySQL, adding configuration for MariaDB and MySQL default compatibility.
- Fixed all errors with H2, it's now stable and usable in production.
- Added a startup java argument for suppressing all log about the library downloader.
- Added stable support for Velocity (and Forks).
- Added stable support for BungeeCord (and Forks).
- Using now Java 11 and applied A LOT OF CHANGES FOR PERFORMANCE.
- Fixed some rarely errors in backend.
- Improved SQLite performance with adding some execution.
- Updated HikariCP from 4.0.3 to 6.2.1.
- Added Negativity API (unlimited usage).
THIS UPDATE DOESN'T REQUIRE RESET YOUR CONFIG, YOU CAN COMPARE YOUR CONFIG.YML WITH THE .JAR INSIDE IF YOU WANT GET SOME LITTLE CHANGES.
1.0.5-pre5
Jan 15, 2025
Version 1.0.5-pre2
(showing updates from 1.0.4 -> 1.0.5-pre5) - This version has been launched for public for testing, this seems to be stable, but if you find errors or problems, please, JOIN TO THE DISCORD SUPPORT.
Changelogs:
- Added IPRisk API (unlimited usage).
- Added FreeIPAPI.
- Increased max_flags option to 3 for better avoid false flags for the amount of free APIs.
- Added IPdb-Amelia API (unlimited usage).
- Disabled SkyDB by default in configuration because their big delay in response.
- Fixed value to check for VPN in case the API return in array list.
- Added option to use value with array list. (this feature was added for IPdb-Amelia, for better results)
- Added reload command for the plugin.
- Fixed bypass permission.
- Added auto-complete for add/remove sub-arguments.
- Fixed Folia support.
- Implemented a little API for developers.
- Download their dependencies automatically when the server start, so you can use MySQL and SQLite in Proxy (BungeeCord/Velocity).
- Added support for MiniMessage.
- Added support for new databases: MariaDB, PostgreSQL and H2 with HikariCP.
- Added new command /foxgate db; in this you can purge the database, all saved IP's (/foxgate db purge) and reconnect the database if you applied changes and you don't want restart your server (/foxgate db reconnect).
- Added new command /foxgate status, with this you can see information from an IP saved in the database.
- Improved the structure in the config.yml.
- Updated and fixed some fields in the API.
- Fixed in Velocity backends, this only detecting IP of host.
- Fixed a lot of errors in 1.0.4 version.
- Changed PlayerPreLoginEvent to AsyncPlayerPreLoginEvent for better performance.
- Added default values in case your config is older. RECOMMENDED TO RESET IN UPDATES!
THIS UPDATE ONLY WORKS IN BACKEND, PROXY GO TO WILL BE SUPPORTED IN 1.0.5 (FINAL VERSION OF THIS PRE-VERSIONS). ALSO THIS VERSION REQUIRE RESET YOUR CONFIGURATION FILE FOR APPLY ALL NEW CHANGES!
1.0.5-pre2
Nov 15, 2024
Version 1.0.5-pre2
1.0.5-pre2:
- Fixed loading in Velocity (still in experimental)
1.0.5-pre1:
- Added Velocity (experimental) support.
1.0.4
Sep 19, 2024
Page 1
