Symptoms
- Unable to install Plugins in JetBackup 5
- Unable to update Plugins in JetBackup 5 (Sometimes leading to Fatal Errors)
- Plugin returning Fatal error: SourceGuardian Loader - This protected script was not encoded for version 8.x.x of PHP
- Error: Invalid repo URL provided when entering valid URL.
Cause
The "Invalid repo URL provided" is a hard-coded error message; it does not indicate the URL is invalid. This error can be caused by a network connectivity issue where your client machine is attempting to resolve the repository's hostname to an IPv6 address, but your network's firewall, access control list (ACL), or routing configuration is blocking or improperly handling IPv6 traffic.
Even if the repository host is reachable over IPv4, your system may default to the non-functional IPv6 route, causing the connection to fail.
Resolution
To diagnose and resolve this issue, you can use the curl command-line tool to test connectivity to the repository host over both IPv4 and IPv6 explicitly.
Step 1: Test Connectivity to the JetApps Repository with IPv4
First, test the repository connection with -4 (IPv4) and verbose (-v) flag. This will show whether your server can connect via IPv4.
curl -4 -v https://repo.jetlicense.com/plugins/
If it's is working correctly, you should see output that includes "Connected to repo.jetlicense.com" or "Proudly Served by LiteSpeed Web Server at repo.jetlicense.com Port 443".
Step 2: Test Connectivity to the JetApps plugin Repo via IPv6
Next, perform the same test, but force curl to use IPv6. This step confirms if IPv6 is the source of the problem.
Run the same command, but replace the -4 flag with -6.
curl -6 -v https://repo.jetlicense.com/plugins/If this command hangs, times out, or returns a "Could not connect to host" error, you have confirmed that traffic over IPv6 is being blocked somewhere between your machine and the repository host. This is an example of a broken IPv6 configuration on the local server:
* curl -v https://repo.jetlicense.com/plugins/
* About to connect() to repo.jetlicense.com port 443 (#0) * Trying 2a03:b0c0:2:d0::16a1:7001... * Connection timed out * curl -6 -v https://repo.jetlicense.com/plugins/ * Trying 2a03:b0c0:2:d0::16a1:7001:443... * Immediate connect fail for 2a03:b0c0:2:d0::16a1:7001: Network is unreachable * Trying 2a03:b0c0:3:d0::18e3:d001:443... * Immediate connect fail for 2a03:b0c0:3:d0::18e3:d001: Network is unreachable * Closing connection 0 curl: (7) Couldn't connect to server
You can try another IPv6-compatible domain such as Google.com to verify the problem is the local IPv6 connection.
* curl -v google.com
* About to connect() to google.com port 80 (#0) * Trying 2404:6800:4009:806::200e... * Connection timed out
The primary solution is to update your organization's firewall or network security rules to allow traffic to remote IPv6 addresses. If the curl test in Step 2 failed, you will need to contact your network administrator regarding the issue with IPv6.
Temporary Workaround
As a temporary workaround, you can force IPv4 by adding the repository to your /etc/hosts file.
207.154.206.128 repo.jetlicense.com
64.225.76.83 repo.jetlicense.com
You can find the IPv4 addresses for the repository using the nslookup command.
nslookup repo.jetlicense.com
It is important to note that this is a temporary solution, and does not resolve the underlying issue. If you are experiencing issues when curling other sites, you will need to work with your systems/network administrator to resolve this.
If you require further assistance to resolve the issue, please contact support.
