# File Upload with GridFS not working - how can i change to local filesystem?

**URL:** <https://forums.rocket.chat/t/file-upload-with-gridfs-not-working-how-can-i-change-to-local-filesystem/5045>\
**Category:** Community Support\
**Created:** [November 12, 2019, 6:35am UTC](https://forums.rocket.chat/t/file-upload-with-gridfs-not-working-how-can-i-change-to-local-filesystem/5045 "2019-11-12T06:35:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![phatair](https://avatars.discourse-cdn.com/v4/letter/p/94ad74/32.png) [@phatair](https://forums.rocket.chat/u/phatair)\
**Post date:** [November 12, 2019, 6:35am UTC](https://forums.rocket.chat/t/file-upload-with-gridfs-not-working-how-can-i-change-to-local-filesystem/5045/1 "2019-11-12T06:35:22Z")

</div>

### Description

Hello, we are testing at the moment rocket.chat in our company.  
The System is working fine but file upload is not working. If we add a file the upload stuck on 0%.

If i check the “show logs” in the admin backend, i dont see any information about the upload process.

I thought a good solution will be to change the upload to local filesystem but where should i place the files? In the snap path /var/snap/rocketchat-server/common ?

Can someone help me with this question or how to solve the GridFS Problem?  
Thank you.

### Server Setup Information

- Version of Rocket.Chat Server: 2.1.1
- Operating System: Ubuntu 18.04.3
- Deployment Method: snap
- Number of Running Instances: 1
- DB Replicaset Oplog:
- NodeJS Version: 8.15.1
- MongoDB Version: 3.6.14
- Proxy: caddy
- Firewalls involved: no

---

<div class="post-metadata">

**Author:** ![phatair](https://avatars.discourse-cdn.com/v4/letter/p/94ad74/32.png) [@phatair](https://forums.rocket.chat/u/phatair)\
**Post date:** [November 12, 2019, 12:15pm UTC](https://forums.rocket.chat/t/file-upload-with-gridfs-not-working-how-can-i-change-to-local-filesystem/5045/2 "2019-11-12T12:15:27Z")

</div>

GridFS is working now.  
I had a config error - the website url was set in Rocket.Chat to [https://chat.domain.com:3000](https://chat.domain.com:3000)  
We caddy as proxy so the :3000 was wrong.

Just one question to the local filesystem config.  
If i set it to filesystem and set the path for the file system to /var/snap/rocketchat-server/common/upload, is this correct? Then i set the permission for this folder to 755 and root:root

Thank you

---

<div class="post-metadata">

**Author:** ![lucia.guevgeozian](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/lucia.guevgeozian/32/447_2.png) [@lucia.guevgeozian](https://forums.rocket.chat/u/lucia.guevgeozian)\
**Post date:** [November 20, 2019, 2:44pm UTC](https://forums.rocket.chat/t/file-upload-with-gridfs-not-working-how-can-i-change-to-local-filesystem/5045/3 "2019-11-20T14:44:14Z")

</div>

Hi, yes that should work, this folder allows access and modification /var/snap/rocketchat-server/common

---

<div class="post-metadata">

**Author:** ![xtvjxk123456](https://avatars.discourse-cdn.com/v4/letter/x/7feea3/32.png) [@xtvjxk123456](https://forums.rocket.chat/u/xtvjxk123456)\
**Post date:** [November 26, 2019, 1:59am UTC](https://forums.rocket.chat/t/file-upload-with-gridfs-not-working-how-can-i-change-to-local-filesystem/5045/4 "2019-11-26T01:59:36Z")

</div>

my linux has some issue in upload files.  
success in sending emoje, changing profile photo use local image.  
faild in uploading file in any chat room.

ps: i am noob in linux system  
my server:  
 ![Snipaste_2019-11-26_09-58-31](https://us1.discourse-cdn.com/flex021/uploads/rocketchat/original/2X/e/e95960f29b1e8a7e4110a8be5e58bec5578105ad.jpeg)  
deployed by snapd

thanks for your help.

---

<div class="post-metadata">

**Author:** ![captainwasabi](https://avatars.discourse-cdn.com/v4/letter/c/67e7ee/32.png) [@captainwasabi](https://forums.rocket.chat/u/captainwasabi)\
**Post date:** [March 23, 2020, 3:23pm UTC](https://forums.rocket.chat/t/file-upload-with-gridfs-not-working-how-can-i-change-to-local-filesystem/5045/5 "2020-03-23T15:23:46Z")

</div>

@phatair Had a similar problem, the url was set to http:// instead of https://…
