Server returned HTTP response code: 522

Any questions? Need some help?
Post Reply
saides
Posts: 1
Joined: 24 Aug 2018, 14:07

Server returned HTTP response code: 522

Post by saides »

Im using filebot on a headless ubuntu 16.04 installation with rTorrent and the rtorrent post-processing script and its been working great so far with both tv shows and movies but when i finished downloading a anime episode i get this error in my amc.log.
I tried to use the windows client as well but it didn't want to work there either.

Code: Select all

Fetch failed: Try again in 5 seconds (2 more) => java.io.IOException: Server returned HTTP response code: 522 for URL: https://api.filebot.net/v4/data/anidb.txt.xz
Fetch failed: Try again in 10 seconds (1 more) => java.io.IOException: Server returned HTTP response code: 522 for URL: https://api.filebot.net/v4/data/anidb.txt.xz
Fetch failed: https://api.filebot.net/v4/data/anidb.txt.xz
java.io.IOException: Server returned HTTP response code: 522 for URL: https://api.filebot.net/v4/data/anidb.txt.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.media.ReleaseInfo.lambda$resource$19(ReleaseInfo.java:490)
        at net.filebot.MemoizedResource.get(Resource.java:36)
        at net.filebot.media.ReleaseInfo.getAnidbIndex(ReleaseInfo.java:376)
        at net.filebot.media.MediaDetection.lambda$getAnimeIndex$3(MediaDetection.java:501)
        at net.filebot.media.MediaDetection.getIndex(MediaDetection.java:859)
        at net.filebot.media.MediaDetection.getAnimeIndex(MediaDetection.java:499)
        at net.filebot.media.MediaDetection.detectSeriesNames(MediaDetection.java:323)
        at net.filebot.cli.ScriptShellBaseClass.detectSeriesName(ScriptShellBaseClass.java:261)
        at net.filebot.cli.ScriptShellBaseClass.detectAnimeName(ScriptShellBaseClass.java:253)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at Script1$_run_closure50.doCall(Script1.groovy:337)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at Script1.run(Script1.groovy:321)
        at net.filebot.cli.ScriptShell.evaluate(ScriptShell.java:64)
        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: 522 for URL: https://api.filebot.net/v4/data/anidb.txt.xz
        at net.filebot.web.WebRequest.fetch(WebRequest.java:139)
        ... 30 more

User avatar
rednoah
The Source
Posts: 22998
Joined: 16 Nov 2011, 08:59
Location: Taipei
Contact:

Re: Unable to rename anime

Post by rednoah »

522 is a temporary server-side connection issue that'll probably just go away by itself if you try again a bit later.
:idea: Please read the FAQ and How to Request Help.
Post Reply