<p>I have a page where updating the asset indexes is not working.</p>

<p>If I hit «Update asset indexes» The loading animation shows and never stops the animation.</p>

<ul>
<li>Installed <a href="https://github.com/ostark/craft-async-queue" rel="nofollow noreferrer">AsyncQueue</a> = Same effect</li>
<li>Increased memory_limit to 128M</li>
<li>max_execution_time is set to 30</li>
<li>There are no stuck tasks</li>
<li>php 7.0.33</li>
<li>CraftCMS 3.15</li>
</ul>

<p>It works locally (MAMP Apache) so I guess it must be a server thing?!</p>

<p>There are about 10 pdf &amp; jpg assets so it's not a lot.</p>

<p>What else can I do?</p>

CC BY-SA 4.0
2019-02-13T16:04:45.450Z
Do you see any errors in your Javascript or Network console? You can also index assets from the cli tool using this command: ./craft index-assets/all
Tony DeStefano
CC BY-SA 4.0
2019-03-18T17:55:46.747Z
Are you using a remote volume like S3 and storing the access keys as .env vars, and did you forget to populate them after deploying to a new environment? Because that’s what I just did.
Dom Stubbs
CC BY-SA 4.0
2019-03-19T08:07:59.753Z
No remote volume like s3
KSPR
<craft3><tasks>
Updating asset indexes doesn't work
# Updating asset indexes doesn't work

(Asked by: username_0 on 2019-02-13)

I have a page where updating the asset indexes is not working.

If I hit «Update asset indexes» The loading animation shows and never stops the animation.

* Installed [AsyncQueue](https://github.com/ostark/craft-async-queue) = Same effect
* Increased memory\_limit to 128M
* max\_execution\_time is set to 30
* There are no stuck tasks
* php 7.0.33
* CraftCMS 3.15

It works locally (MAMP Apache) so I guess it must be a server thing?!

There are about 10 pdf & jpg assets so it's not a lot.

What else can I do?

**Tags:** craft3, tasks
> **Comments:**
> **username_1**: Do you see any errors in your Javascript or Network console? You can also index assets from the cli tool using this command: ./craft index-assets/all  
> **username_2**: Are you using a remote volume like S3 and storing the access keys as .env vars, and did you forget to populate them after deploying to a new environment? Because that’s what I just did.  
> **username_0**: No remote volume like s3  

---

## 0 answers

