# Cannot reach collections after upgrading to v8

**URL:** <https://community.forestadmin.com/t/cannot-reach-collections-after-upgrading-to-v8/6506>\
**Category:** Help me!\
**Created:** [July 17, 2023, 9:27am UTC](https://community.forestadmin.com/t/cannot-reach-collections-after-upgrading-to-v8/6506 "2023-07-17T09:27:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Soufiane](https://avatars.discourse-cdn.com/v4/letter/s/8edcca/32.png) [@Soufiane](https://community.forestadmin.com/u/Soufiane)\
**Post date:** [July 17, 2023, 9:27am UTC](https://community.forestadmin.com/t/cannot-reach-collections-after-upgrading-to-v8/6506/1 "2023-07-17T09:27:47Z")

</div>

## Feature(s) impacted

I am upgrading a project from the version 7 to 8.  
When upgrating to v8, I cannot reach collections.

## Observed behavior

## Context

- Project name: Sergic
- Team name: Gestion
- Environment name: Development
- Agent (forest package) name & version: 7.12.3 to 8.5.14
- Database type: Postgres
- Recent changes made on your end if any: upgrade to v8

---

<div class="post-metadata">

**Author:** ![anon33050819](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@anon33050819](https://community.forestadmin.com/u/anon33050819)\
**Post date:** [July 17, 2023, 10:12am UTC](https://community.forestadmin.com/t/cannot-reach-collections-after-upgrading-to-v8/6506/3 "2023-07-17T10:12:21Z")

</div>

> [@Soufiane](#):
>
> Sergic

Hi @Soufiane ,  
Do you have any error messages in your console?

---

<div class="post-metadata">

**Author:** ![Soufiane](https://avatars.discourse-cdn.com/v4/letter/s/8edcca/32.png) [@Soufiane](https://community.forestadmin.com/u/Soufiane)\
**Post date:** [July 17, 2023, 11:53am UTC](https://community.forestadmin.com/t/cannot-reach-collections-after-upgrading-to-v8/6506/4 "2023-07-17T11:53:03Z")

</div>

In my console , I have this message:

Access to XMLHttpRequest at ‘[http://localhost:3310/forest/places?timezone=Europe%2FParis&fields[places]=sergicIdFull%2CdisplayName%2Cadresse%2CupdatedAt%2Cgestionnaire%2Cassistant%20copro%2Ccomptable%2CfiscalYearMonth%2CintegrationState%2CregistrationNumber%2Ckind&filters={“field”%3A"integrationState"%2C"operator"%3A"equal"%2C"value"%3A"done"}&page[number]=1&page[size]=15&sort=-id](http://localhost:3310/forest/places?timezone=Europe%2FParis&fields%5Bplaces%5D=sergicIdFull%2CdisplayName%2Cadresse%2CupdatedAt%2Cgestionnaire%2Cassistant%20copro%2Ccomptable%2CfiscalYearMonth%2CintegrationState%2CregistrationNumber%2Ckind&filters=%7B%22field%22%3A%22integrationState%22%2C%22operator%22%3A%22equal%22%2C%22value%22%3A%22done%22%7D&page%5Bnumber%5D=1&page%5Bsize%5D=15&sort=-id)’ from origin ‘[https://app.forestadmin.com](https://app.forestadmin.com)’ has been blocked by CORS policy: Request header field forest-context-url is not allowed by Access-Control-Allow-Headers in preflight response

---

<div class="post-metadata">

**Author:** ![anon7284711](https://avatars.discourse-cdn.com/v4/letter/a/ac8455/32.png) [@anon7284711](https://community.forestadmin.com/u/anon7284711)\
**Post date:** [July 19, 2023, 10:11am UTC](https://community.forestadmin.com/t/cannot-reach-collections-after-upgrading-to-v8/6506/5 "2023-07-19T10:11:46Z")

</div>

Hello @Soufiane,

I’m coming back to you as this topic has not been answered nor marked as resolved.

The error you got is linked to a [breaking change while upgrading to v8](https://docs.forestadmin.com/documentation/extra-help/maintain/upgrade-notes-sql-mongodb/upgrade-to-v8#cors-allowed-headers), as shared on [the other topic](https://community.forestadmin.com/t/smart-action-hooks-change-doesnt-work-when-upgrating-to-v8/6508/3).

Do you still encounter issues or can we mark this as resolved ?

Best regards,