Jump to content

Recommended Posts

Posted

I've been running this for a long while now with Wasabi as my storage.  Everything has been running great.  Since the last IPS update; I'm getting more and more reports of the following:

<Error>
<Code>InternalError</Code>
<Message>We encountered an internal error. Please retry the operation again later.</Message>
<Detail>Get "http://10.21.30.227:31361/P-8285495795441406882/B-00616654/O-bed2594b50cd1f68/S-1": dial tcp 10.21.17.142:0->10.21.30.227:31361: bind: address already in use</Detail>
<RequestId>C86927E37DC10387:A</RequestId>
<HostId>nMstRzjpqhf/HN87leABU8e5r40S9eI4iFxMP8FBT1LWm5IxDY2dxdDSU0nCFUyfZJlJlXSTKdz7</HostId>
</Error>

I don't' know where this error is actually coming from. Not sure if this is Cloudlfare, Wasabi, IPS, or my server.  This just seems to happen every now and then when clicking to download a file.

  • 2 weeks later...
Posted (edited)

So, I got this to work with Wasabi after some setup but now my transfer of files have been stuck at 54% since almost two weeks back. I've verified that cron is working and tried to start the transfer manually with no success.

My question is if I would go through the hassle of moving files manually (downloading and uploading) will the system take notice of this and finish the automatic move when it verifies that the files are already at the destination?

Edited by Sirmadsen
Posted (edited)

Images stored at my Wasabi bucket are not are showing on my site. They have been moved (from S3) and I have verified that they are in fact in the bucket and can be opened and viewed from Wasabi, but they just show a broken image icon on my site. I have tried with Cloudflare on and paused.

I am now out of ideas.

Edited by Sirmadsen
Posted
10 minutes ago, Randy Calvert said:

Can you directly access the Wasabi URL for the object?  There is a chance your permissions are incorrect.  

Not from my site no, I get

"This site can’t be reached

cdn.throneofgeeks.com’s DNS address could not be found.

DNS_PROBE_POSSIBLE"

I have my bucket set public.

Posted
1 hour ago, Randy Calvert said:

Cloudflare is saying the entry you have for "cdn" is incorrect.  What value do you have there?

Not entirely sure what you mean but if it's the CNAME CDN we set up from the tutorial I have

cdn.throneofgeeks.com.s3.eu-central-1.wasabisys.com

Posted

On a hunch, I turned of my VPN and everything seems to work after that. Guess Cloudflare don't like VPN. Am also pretty sure I saw a setting somewhere in Cloudflare about VPN but now I can't find it again.

  • 11 months later...
Posted (edited)

Does this guide still require the (missing) plugin linked in the first post?

There is a post on page 5 that mentions a fix included in 4.5.4, but not sure if it still requires the plugin even after that.

 

With the marketplace closed, I'm not seeing the S3 Compatible Downloads application listed on @All Astronauts's site.

Edited by teraßyte
Posted

We are currently running version 4.7.14 and I would like to use Wasabi or any other similar service that is cheaper than S3. Does anyone have an update?

Posted

I still use this Wasabi + Cloudflare setup.  I cannot emphasize how much cheaper it is than Amazon S3 + Cloud front. The bandwidth fees would be hundreds of dollars (if not thousands) for my website that is media rich.  Instead, I pay zero in bandwidth fees and $5.99 per terabyte of storage.  

Posted
47 minutes ago, Joel R said:

I still use this Wasabi + Cloudflare setup.  I cannot emphasize how much cheaper it is than Amazon S3 + Cloud front. The bandwidth fees would be hundreds of dollars (if not thousands) for my website that is media rich.  Instead, I pay zero in bandwidth fees and $5.99 per terabyte of storage.  

What I'd like to know is if the fix IPS added in 4.5.4 allows the use of Wasabi without any 3rd party plugin/application.

After my post above, I tried looking at the code, and I think it's impossible since there are some hardcoded Amazon URLs/values.

  • 2 months later...
  • 1 month later...
Posted

Wasabi is currently experiencing an outage on US-East-1 and US-East-2 due to a cooling issue in their data center. They call it a "slowdown," but when all your CSS, JS, and image files come back with a timeout, it's an outage. 

Posted

Received this:

 

Degraded performance in US-EAST-1 and US-EAST-2 regions
An update has been posted
A recovery operation is currently underway to bring back the impacted systems. This will take between 6 to 12 hours to complete. We will continue to update here as progress is made.
Time posted
May 30, 19:29 UTC
Components affected
    US-East-1 (N. Virginia)
    US-East-2 (N. Virginia)
    Wasabi Management Console
 

×
×
  • Create New...