[BUG] Error log for 4 sites in first launch

[M4RCK5]

2024-03-23 12:55:11.937235 | v1.4.1 | Error: An error occurred while checking Transfer! Please report this. Exception: HTTPSConnectionPool(host='transfer.sh', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x00000157CC7A6DD0>, 'Connection to transfer.sh timed out. (connect timeout=5)')) | Additional Info: <Response [200]>

2024-03-23 12:56:01.801697 | v1.4.1 | Error: An error occurred while checking Keep! Please report this. Exception: HTTPSConnectionPool(host='keep.sh', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x00000157CC7A5850>: Failed to resolve 'keep.sh' ([Errno 11001] getaddrinfo failed)")) | Additional Info: <Response [200]>

2024-03-23 12:56:25.848010 | v1.4.1 | Error: An error occurred while checking Fastupload! Please report this. Exception: ("Connection broken: InvalidChunkLength(got length b'', 0 bytes read)", InvalidChunkLength(got length b'', 0 bytes read)) | Additional Info: <Response [200]>

2024-03-23 12:57:40.205901 | v1.4.1 | Error: An error occurred while checking Keep! Please report this. Exception: HTTPSConnectionPool(host='keep.sh', port=443): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPSConnection object at 0x00000268F453DC10>: Failed to resolve 'keep.sh' ([Errno 11001] getaddrinfo failed)")) | Additional Info: <Response [200]>

[Official-Husko]

Thank you for your report. I will take a look at it in a bit. What i can already say is that its likely they were down at the time or that they changed something in the backend.

[Official-Husko]

After checking it again it seems like this:

1. transfer.sh timed out. Transfer tends to be a slow fuck sometimes.
2. Keep.sh was either down at the time, is blocked from your connection or if you used proxies then it was probably blacklisted.
3. Fastupload somehow fucked up sending things from what it seems. I will investigate that.

Edit: Keep is indeed down.

Also Transfer.sh is shitting the bed again. They have internal Server errors. Nothing i can do about that.

[Official-Husko]

After further testing i was not able to recreate any issues except for transfer being slow as shit which sometimes causes that error and keep.sh being down. Nothing i can do about these for now.

If the issue should still persist on your end then feel free to comment on this issue again and i will reopen it for further investigation.