# Shares and Public links inaccessible after migration and upgrade

**URL:** <https://forum.pydio.com/t/shares-and-public-links-inaccessible-after-migration-and-upgrade/1150>\
**Category:** Pydio 8\
**Tags:** php70, debian\
**Created:** [May 22, 2018, 3:59pm UTC](https://forum.pydio.com/t/shares-and-public-links-inaccessible-after-migration-and-upgrade/1150 "2018-05-22T15:59:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eric\_blvr](https://avatars.discourse-cdn.com/v4/letter/e/c77e96/32.png) [@eric\_blvr](https://forum.pydio.com/u/eric_blvr)\
**Post date:** [May 22, 2018, 3:59pm UTC](https://forum.pydio.com/t/shares-and-public-links-inaccessible-after-migration-and-upgrade/1150/1 "2018-05-22T15:59:07Z")

</div>

Hi, I’m working on a two part migration. First we’re upgrading from Pydio 6 to 8, and we’re migrating to a new server. The upgrade from 6 to 8 has been relatively smooth, simply ran the migration SQL files off of GitHub, replaced the core files with the 8 files, and re-upgraded to Enterprise.

I’m running into an issue with the server migration. Once on the new server none of the public links work (I’ve gotten rid of the /data/public directory and redirected all requests to /public instead, but they all 404 either way), and all of the shares are throwing errors (ShareCenter.php - Error while loading share. Error was (cannot find file…)) because they’re looking for the shares in the old location.

I attempted to do a find/replace on the database to update the file locations to their new absolute paths, but that resulted in all sorts of things breaking.

---

<div class="post-metadata">

**Author:** ![zayn](https://avatars.discourse-cdn.com/v4/letter/z/a87d85/32.png) [@zayn](https://forum.pydio.com/u/zayn)\
**Post date:** [June 18, 2018, 8:04am UTC](https://forum.pydio.com/t/shares-and-public-links-inaccessible-after-migration-and-upgrade/1150/2 "2018-06-18T08:04:11Z")

</div>

Hi,  
what are your mysql, php and os versions.