• Welcome to the Chevereto user community!

    Here users from all over the world gather around to learn the latest about Chevereto and contribute with ideas to improve the software.

    Please keep in mind:

    • 😌 This community is user driven. Be polite with other users.
    • 👉 Is required to purchase a Chevereto license to participate in this community (doesn't apply to Pre-sales).
    • 💸 Purchase a Pro Subscription to get access to active software support and faster ticket response times.
  • Chevereto Support CLST

    Support response

    Support checklist

    • ⚠️ Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • ✅ Confirm that the server meets the System Requirements
    • 🔥 Check for any available Hotfix - your issue could be already reported/fixed
    • 📚 Read documentation - It will be required to Debug and understand Errors for a faster support response

Cloud Block Storage

WastelandBuddha

Chevereto Member
I'm having an issue with External Storage, and keep running up against an issue that I can't get past. I'm sure I'm missing something minor, and have searched for fixes without any luck.

My setup is pretty simple. I'm running a VPS, and attaching a 200GB cloud block storage instance to it, which I mount at /mnt/cbs01. I've got php7.3, NGINX, and MariaDB all running the application without an issue. In Chevereto, I go into External Storage, click "add", and then select local disk. I put in the path /mnt/cbs01, and make sure that www-data owns everything under that folder.

The one thing I'm unsure of, is the URL to give it for mapping, but I've tried several different things and none have worked. When I upload images, there are no errors. It writes the images to /mnt/cbs01 without issue, but then displays IMAGE NOT FOUND on every image afterward. This is where I'm stuck. If I disable the external storage and upload again, everything works as it should. It installs to /images, and displays images. It's only when I try to use a different path on the same server that things go sideways.

Anyone have any thoughs? It would be greatly appriciated.

Phil
 
Hi Phil,

Based in what you describe, the problem can be narrowed to not being able to serve the actual image files for the /mnt/cbs01 path. When this happens is either permissions or because your HTTP server is not configured to serve this path.

Are you sure that the alleged path is being HTTP served?
 
Hey Rodolfo, thank you for the reply!

I suspect I don't have that path in NGINX properly, but honestly, I'm unsure what the syntax would be. Would you be able to post what the declarations would be assuming /mnt/cbs01 is the target I'm after?
 
Back
Top