License Error: Server returned HTTP response code: 403

[daemonofchaos]

I am running filebot:node docker container and when I attempt to activate my license I receive:

Code: Select all

License Error: Server returned HTTP response code: 403 for URL: https://license.filebot.net/verify/P4057755

My license file has been working fine since Mid July when I bought it. Any ideas what is going on and how I can fix it?

[rednoah]

1.
Please run filebot -script fn:sysinfo and post the output, so we can see what version / revision you're running.


2.
Are you using the final release of FileBot 4.8.2 (published on 8 August 2018) or some prior pre-release revision? If you're using an older build, then you may need to install the final release:
https://get.filebot.net/filebot/FileBot_4.8.2/

[daemonofchaos]

I'm running the latest docker filebot:node container docker pull rednoah/filebot:node and have the following output from docker logs on the container:

Code: Select all

ENVIRONMENT { FILEBOT_CMD_UID: '0',
  HOSTNAME: '12aca3c08f08',
  HOME: '/data',
  FILEBOT_NODE_AUTH: 'NONE',
  JAVA_VERSION: '10.0.2+13',
  FILEBOT_NODE_HTTP_PORT: '5452',
  FILEBOT_NODE_VERSION: '0.2.8.1',
  JAVA_DEBIAN_VERSION: '10.0.2+13-1',
  FILEBOT_VERSION: '4.8.2',
  PATH:
   '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin',
  FILEBOT_NODE_HOST: '0.0.0.0',
  FILEBOT_NODE_HTTP: 'YES',
  LANG: 'C.UTF-8',
  DOCKER_VOLUME: '/volume1',
  FILEBOT_CMD_GID: '0',
  FILEBOT_OPTS: '-Dapplication.deployment=docker -Duser.home=/data',
  JAVA_HOME: '/docker-java-home',
  DOCKER_DATA: '/data',
  PWD: '/usr/local/filebot-node',
  FILEBOT_CMD: 'filebot',
  FILEBOT_NODE_CLIENT: '/usr/local/filebot-node/client',
  FILEBOT_CMD_CWD: '/volume1' }
USER { UID: 0, GID: 0 }
filebot-node listening at http://0.0.0.0:5452/filebot/

When I click on Tools > System Info, I receive:

Code: Select all

filebot -script 'fn:sysinfo'

------------------------------------------

Fetch failed: Try again in 5 seconds (2 more) => java.io.IOException: Server returned HTTP response code: 403 for URL: https://api.filebot.net/v4/script/fn.jar.xz
Fetch failed: Try again in 10 seconds (1 more) => java.io.IOException: Server returned HTTP response code: 403 for URL: https://api.filebot.net/v4/script/fn.jar.xz
Fetch failed: https://api.filebot.net/v4/script/fn.jar.xz
java.io.IOException: Server returned HTTP response code: 403 for URL: https://api.filebot.net/v4/script/fn.jar.xz
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
	at net.filebot.web.WebRequest.fetch(WebRequest.java:142)
	at net.filebot.CachedResource.lambda$fetchIfModified$9(CachedResource.java:215)
	at net.filebot.CachedResource.lambda$get$0(CachedResource.java:87)
	at net.filebot.CachedResource.retry(CachedResource.java:121)
	at net.filebot.CachedResource.retry(CachedResource.java:133)
	at net.filebot.CachedResource.retry(CachedResource.java:133)
	at net.filebot.CachedResource.lambda$get$1(CachedResource.java:87)
	at net.filebot.Cache.computeIf(Cache.java:90)
	at net.filebot.CachedResource.get(CachedResource.java:82)
	at net.filebot.MemoizedResource.get(Resource.java:36)
	at net.filebot.cli.ScriptBundle.getScript(ScriptBundle.java:32)
	at net.filebot.cli.ScriptShell.runScript(ScriptShell.java:74)
	at net.filebot.cli.ArgumentProcessor.runScript(ArgumentProcessor.java:154)
	at net.filebot.cli.ArgumentProcessor.run(ArgumentProcessor.java:36)
	at net.filebot.Main.main(Main.java:131)
Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: https://api.filebot.net/v4/script/fn.jar.xz
	at net.filebot.web.WebRequest.fetch(WebRequest.java:139)
	... 14 more

Server returned HTTP response code: 403 for URL: https://api.filebot.net/v4/script/fn.jar.xz
java.io.IOException: Server returned HTTP response code: 403 for URL: https://api.filebot.net/v4/script/fn.jar.xz
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
	at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
	at net.filebot.web.WebRequest.fetch(WebRequest.java:142)
	at net.filebot.CachedResource.lambda$fetchIfModified$9(CachedResource.java:215)
	at net.filebot.CachedResource.lambda$get$0(CachedResource.java:87)
	at net.filebot.CachedResource.retry(CachedResource.java:121)
	at net.filebot.CachedResource.retry(CachedResource.java:133)
	at net.filebot.CachedResource.retry(CachedResource.java:133)
	at net.filebot.CachedResource.lambda$get$1(CachedResource.java:87)
	at net.filebot.Cache.computeIf(Cache.java:90)
	at net.filebot.CachedResource.get(CachedResource.java:82)
	at net.filebot.MemoizedResource.get(Resource.java:36)
	at net.filebot.cli.ScriptBundle.getScript(ScriptBundle.java:32)
	at net.filebot.cli.ScriptShell.runScript(ScriptShell.java:74)
	at net.filebot.cli.ArgumentProcessor.runScript(ArgumentProcessor.java:154)
	at net.filebot.cli.ArgumentProcessor.run(ArgumentProcessor.java:36)
	at net.filebot.Main.main(Main.java:131)
Caused by: java.io.IOException: Server returned HTTP response code: 403 for URL: https://api.filebot.net/v4/script/fn.jar.xz
	at net.filebot.web.WebRequest.fetch(WebRequest.java:139)
	... 14 more

Failure (°_°)
------------------------------------------

[Process error]

[rednoah]

Looks like we get Server returned HTTP response code: 403 for all kinds of services, so FileBot won't work regardless of license activation. That might indicate that your public IP has been blacklisted by CloudFlare.

What does curl say if you run the same request from the same machine?

Code: Select all

curl -I https://api.filebot.net/v4/script/fn.jar.xz

You will need log into the container and run this command. See docker manual for details on how to log into a container and run commands.

If this is a remote server, seedbox, etc, and has VPN, then you can try to use VPN from your desktop, and then access the internet via this remote machine, and then see if you get the same 403 error messages.

[daemonofchaos]

That was indeed the problem. As soon as I disabled my VPN everything started working successfully.

Thank you very much for the assist.