Mail: [email protected] Phone: +1(424)231-4091

Broken Media Images

There are multiple reasons why images might not show on your NexoPOS 4.x installation. This guide will go through the different steps you need to covert in order to fix this problem.

Storage is not symlinked

Probably during the installation of NexoPOS 4.x, you've forgotten to create a symbolic link for your store. Since media are saved on a Storage directory, those images will successfully be uploaded, but won't appear (will appear as broken). The solution for this is to create a symbolic link using this command :

php artisan storage:link

Wrong APP_URL Value

While editing the .env file, you might have omitted to add either the http:// or the https:// as the prefix for your APP_URL value. Here is a bad example of the APP_URL value:

Here is what it should look like instead:

There are various reasons that might cause images not to load on NexoPOS 4x.

We'll try to cover most cases to fix that issue. But in case it still didn't go through, you can reach customer support at [email protected].

Invalid Storage Link

This can happen if you recently moved files. Note that most of the time, symbolic links are absolute, by changing the location of the files, you're making the already created link invalid.

You have two options to fix this issue:

Delete Existing Broken Symlink

You'll need to head to the "public" folder and from there, you'll delete your symbolic link manually (delete the file "storage" on the "public" folder).

Then after that, you need to create a link to the storage as explained above.

Using a Command

You can run a command that will rewrite the existing symlink:

php artisan storage:link --force

Invalid Files Permissions

If the link is created, but the files/directories have invalid permissions, NexoPOS won't be able to access the storage. You need to make sure your files use 644 as permissions and 755 for the folders.

From the CLI, change the directory to the root of NexoPOS and run the following commands.

find -type d -exec chmod 755 {} \;
find -type f -exec chmod 644 {} \;

Your user might have "sudo" capability to execute those commands.