Cloudron Forum

@james and @joseph Thanks for helping

@james How do I do that? And is it needed? I have solved the problem?

I did a brutal problemsolving hack, deleted Grafana and reinstalled it. Now it works.

I think it may have been the "Node Exporter Full" dashboard that was holding the old config in cache, I may have solved it just by deleting the Node Exporter Full and then reinstalled it.

As you see, I have two new endpoints recogniced by Prometheus, but Grafana will not pick up that information

Yes, restarted both after updating "Status - Service discovery" in Prometheus. Even deleted the "prometheus" in Grafana and loaded a new one. It did not pick up on the new services in Prometheus

Hmm....Grafana seems not to pick up on the new sources. And I cant find any refresh/reload button in Grafana. Any advice?

You may set it to "solved"

Ahh...in Prometheus, just click "Status - Service discovery"

But now I experience another problem. Grafana doesnt seem to condsider the new modified prometheus config file. Is there some cache stored in Grafana, or Prometheus, that I need to clear out in order for those two to see the new config file?

Hi @james

Now I see, it was just to skip the port 9090 behind URL. I didn't even consider it possible. Thank you, it worked now

@joseph I tried both with or without https://

I get this error message in Grafana:

Post "http://prometheus.cloudron.tld:9090/api/v1/query": dial tcp xxx.xxx.193.64:9090: i/o timeout - There was an error returned querying the Prometheus API.

Probably stupid question. What port do Prometheus listen on, for Grafana to connect?

I tried http://prometheus.cloudron.tld:9090 (cloudron installation) but that did not work.

@joseph I dont understand this perfectly.

Here is what I did in app terminal

root@e8910a15-341c-4afb-bea1-4feeb79a6ae5:/app/code/wallabag/bin# /app/code/bin/console wallabag:export wallabag --env=prod > /app/data/foo.json
bash: /app/code/bin/console: No such file or directory
root@e8910a15-341c-4afb-bea1-4feeb79a6ae5:/app/code/wallabag/bin# ./console wallabag:export wallabag --env=prod > /app/data/foo.json
PHP Warning:  file_put_contents(/app/code/wallabag/wallabag-export.json): failed to open stream: Read-only file system in /app/code/wallabag/src/Wallabag/CoreBundle/Command/ExportCommand.php on line 64
root@e8910a15-341c-4afb-bea1-4feeb79a6ae5:/app/code/wallabag/bin# 

@joseph nice.

How should that github command be changed to work in the cloudron, either from app terminal or SSH login on the cloudron server?

Wallabag has serveral export options, json, epub, text, csv etc etc, all giving 500 error.

Hi @joseph

This is the only related entry in the logs when I click on "Export"....and example try to export JSON (It is the same whatever export option I choose):

May 05 14:50:12 172.18.0.1 - - [05/May/2025:12:50:10 +0000] "GET /export/unread.json?search_entry%5Bterm%5D= HTTP/1.1" 500 4818 "https://bag.xxxxxxxx.xxxx" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:137.0) Gecko/20100101 Firefox/137.0"

And this error message shows up in wallabag:

@joseph if you read my opening post, you will see that I am fully aware of the procedure. However, in my case I can not export any backup from the old Wallabag, as I get export 500 error whatever way I try to export those more than 3000 stored articles. Thats why I created this post with request for help.

Hi @nebulon

Here is the reason the manual update does not work

Back in the day I did not do what you suggested here https://forum.cloudron.io/post/23720 as I was not aware then of the need to manually update.

So my wallabag version just stayed at version 2.4.1

Now, if I try to manually update, I can't, as there is no update button. There is only the "Check for update" button, and when I click on it the circular arrows rotate, but nothing comes of it. And the logs shows nothing.

@joseph https://forum.cloudron.io/post/23720