<p>You might want to check out the discussion on this <a href="https://github.com/nystudio107/craft-imageoptimize/pull/150" rel="nofollow noreferrer">pull request</a>. Since ImageOptimize uses regular Craft transforms, it's likely that this is something in the AWS S3 plugin.</p>

<p>Indeed, there's an issue <a href="https://github.com/craftcms/aws-s3/issues/22" rel="nofollow noreferrer">400 Bad Request: token expired</a> that appears to be identical. If there's something I can/should be doing to renew the token, I'll definitely make that change.</p>

<p>I'm pending information at the moment.</p>

<p>EDIT: I believe I have found and fixed the issue in the <code>aws-s3</code> package from P&T; I created a <a href="https://github.com/craftcms/aws-s3/pull/61" rel="nofollow noreferrer">pull request</a> to address it.</p>

CC BY-SA 4.0
2019-07-17T08:00:38.393Z
Interesting - we are using the DigitalOcean Spaces Volume plugin which is based on the first-party AWS S3 Volume for Craft - it's likely you have fixed the issue but in another plugin. https://github.com/vaersaagod/dospaces
Dan Lee
CC BY-SA 4.0
2019-07-17T12:43:37.573Z
Are you using the CLI command in ImageOptimize for this? If not, I'd recommend trying it. If you still have issues, perhaps contact the plugin author?
andrew.welch
CC BY-SA 4.0
2019-07-17T14:28:16.320Z
I think I did try - I'll have another go and see how we get on.
Dan Lee
CC BY-SA 4.0
2019-07-16T13:43:26.517Z
2019-07-16T15:50:25.620Z
2019-07-16T15:50:25.620Z
andrew.welch
<p>I have over 1500 images... I'm trying to improve performance on our site and want to create WebP versions of our images.</p>

<p>WebP is installed - new images we upload get converted. When I resave the image variant it begins the process of conversion and optimisation of previous images but then we bump into timeout errors.</p>

<p>What is the best way to do this process in an efficient way? I'd be interested to know how we overcome the timeout error.</p>

<p>Note: </p>

<ul>
<li>images are in a Digital Ocean S3 bucket. </li>
<li>we are using the incredible imageOptimize plugin</li>
<li>we host the site on Laravel Forge</li>
</ul>

<craft3><plugin-imageoptimize>
Converting images to WebP - Overcoming Timeout Errors?
# Converting images to WebP - Overcoming Timeout Errors?

(Asked by: username_0 on 2019-07-16)

I have over 1500 images... I'm trying to improve performance on our site and want to create WebP versions of our images.

WebP is installed - new images we upload get converted. When I resave the image variant it begins the process of conversion and optimisation of previous images but then we bump into timeout errors.

What is the best way to do this process in an efficient way? I'd be interested to know how we overcome the timeout error.

Note:

* images are in a Digital Ocean S3 bucket.
* we are using the incredible imageOptimize plugin
* we host the site on Laravel Forge

**Tags:** craft3, plugin-imageoptimize

---

## 1 answers

### Answer by username_1 on 2019-07-16. Score: 1

You might want to check out the discussion on this [pull request](https://github.com/nystudio107/craft-imageoptimize/pull/150). Since ImageOptimize uses regular Craft transforms, it's likely that this is something in the AWS S3 plugin.

Indeed, there's an issue [400 Bad Request: token expired](https://github.com/craftcms/aws-s3/issues/22) that appears to be identical. If there's something I can/should be doing to renew the token, I'll definitely make that change.

I'm pending information at the moment.

EDIT: I believe I have found and fixed the issue in the `aws-s3` package from P&T I created a [pull request](https://github.com/craftcms/aws-s3/pull/61) to address it.

> **Comments:**
> **username_0**: Interesting - we are using the DigitalOcean Spaces Volume plugin which is based on the first-party AWS S3 Volume for Craft - it's likely you have fixed the issue but in another plugin. https://github.com/vaersaagod/dospaces  
> **username_1**: Are you using the CLI command in ImageOptimize for this? If not, I'd recommend trying it. If you still have issues, perhaps contact the plugin author?  
> **username_0**: I think I did try - I'll have another go and see how we get on.  

---

