Skip to content

Troubleshooting

Jump to bottom
sec77 edited this page Jan 12, 2024 · 13 revisions

here you can find some general tips if you have problems to get Perlite running

Links to other files are not working

You need to change the default link format from Obsidian and after this you maybe need to rebuild your links!


Links to my attachments are not working (the image cant be loaded)

This usually happens if you move a notes file to another location, in this case, unfortunately obsidian does not update the path to your attachment / image, so you need to move your attachment one time to another location to trigger the path update. see issue

The graph is not visible

You need an extra plugin to get the metadata.json, check graph section also make sure the metadata.json resists in the root directory of you vault

I can't Update Perlite

Rebuild and pull the latest images, sometimes (mainly after a new release) docker compose will not recognize that there is a new image on docker hub and so you need to delete your local image first to force docker to pull it again from docker hub

  1. stop all Perlite containers docker-compose down
  2. delete all Perlite images: docker image rm sec77/perlite_web:stable docker image rm sec77/perlite:latest
  3. build the images without cache run docker-compose build --no-cache
  4. run docker-compose up

I can't access Perlite

Check if you can access Perlite from the Host

  1. Check if the port (default 80) is open on you host with ss -tunlp, you should see a line like this:
tcp          LISTEN             0           511          [::]:80             [::]:*

  1. if the port is open, check if you can access the site from your host via curl: curl 127.0.0.1:80 this should give you the html source of Perlite

  2. if you have choosen another port in the docker-compose file, make sure your browser can access it, chrome and firefox have some default blocking for higher ports, which you need to allow first. Default blocked ports in chome

##Check your Nginx Config,

  1. make sure there is only the perlite.conf in the Perlite/web/config directory if you build the perlite_web image, you can proof, that there is only one nginx config with docker exec perlite_web ls -la '/etc/nginx/conf.d' after the container is running
  2. If you have trouble with your own config, try the provided perlite config first

Check the output for errors

  1. Run docker-compose up (without the -d) to see the output on your command line, the output of the first start should look something like this
[+] Running 20/21
 ⠿ web Warning                                                                                                                                                                            1.6s
 ⠿ perlite Pulled 
[...snip...]
[+] Building 7.6s (9/9) FINISHED
[...snip...]
[+] Running 3/3
 ⠿ Network perlite_default  Created                                                                                                                                                       
 ⠿ Container perlite        Created                                                                                                                                                       
 ⠿ Container perlite_web    Created   
Attaching to perlite, perlite_web
perlite      | [11-Jan-2023 07:50:27] NOTICE: fpm is running, pid 1
perlite      | [11-Jan-2023 07:50:27] NOTICE: ready to handle connections
perlite_web  | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
perlite_web  | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
perlite_web  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
perlite_web  | 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf is not a file or does not exist
perlite_web  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
perlite_web  | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
perlite_web  | /docker-entrypoint.sh: Configuration complete; ready for start up
perlite_web  | 2023/01/11 07:50:28 [notice] 1#1: using the "epoll" event method
perlite_web  | 2023/01/11 07:50:28 [notice] 1#1: nginx/1.22.1
perlite_web  | 2023/01/11 07:50:28 [notice] 1#1: built by gcc 10.2.1 20210110 (Debian 10.2.1-6)
perlite_web  | 2023/01/11 07:50:28 [notice] 1#1: OS: Linux 5.15.0-57-generic
perlite_web  | 2023/01/11 07:50:28 [notice] 1#1: getrlimit(RLIMIT_NOFILE): 1048576:1048576
perlite_web  | 2023/01/11 07:50:28 [notice] 1#1: start worker processes
perlite_web  | 2023/01/11 07:50:28 [notice] 1#1: start worker process 20
  1. If you have some warnings or errors in your output, google them.

Perlite runs in a (php) timeout

This can occur if you have a lots of files and links. See issue #97 On the very first page load, Perlite will create a temp file where the linking between the files is stored and used for the graph. If your php engine cant handle this, you can create these temp files by your own via this python script, you need to create the temp files every time the metadata.json has changed.

Nothing of this works, what can I do?

  1. Take a look at some recent issues, maybe:
  1. Join Perlite Discord and use the search or ask in the help channel
  2. Create an issue on github
Clone this wiki locally