# Storagenode stopped working on Pi4 - ERROR: The certificate of 'version.storj.io' is not trusted **URL:** \ **Category:** troubleshooting\ **Tags:** docker, raspberry\ **Created:** [September 20, 2024, 4:43pm UTC](https://forum.storj.io/t/storagenode-stopped-working-on-pi4-error-the-certificate-of-version-storj-io-is-not-trusted/27976 "2024-09-20T16:43:41Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Heinzelschelm](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/heinzelschelm/32/1138_2.png) [@Heinzelschelm](https://forum.storj.io/u/Heinzelschelm)\ **Post date:** [September 20, 2024, 4:43pm UTC](https://forum.storj.io/t/storagenode-stopped-working-on-pi4-error-the-certificate-of-version-storj-io-is-not-trusted/27976/1 "2024-09-20T16:43:41Z")
Hi, my storagenode is not working anymore. Probably it happened after auto-updating via watchtower. The logfile says something about a certificate, that is not trusted and the date in the log also appears very strange for me: --1969-12-31 23:59:59– I am using docker on raspberry pi os (buster). Any idea, what I could do to get it running again? I tried removing and pulling the docker file, but that didn’t help Thanks and kind regards, Hannes ![grafik](https://storj-s3.bcdn.literatehosting.net/original/3X/7/a/7ab3ae5107ea743b8be7abb7db8b6ebfa6b6f34e.png) ---
**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\ **Post date:** [September 20, 2024, 4:46pm UTC](https://forum.storj.io/t/storagenode-stopped-working-on-pi4-error-the-certificate-of-version-storj-io-is-not-trusted/27976/2 "2024-09-20T16:46:06Z")
> The certificate has not yet been activated Cannot get REALTIME clock frequency: Operation not permitted Check clock on your host. ---
**Author:** ![Heinzelschelm](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/heinzelschelm/32/1138_2.png) [@Heinzelschelm](https://forum.storj.io/u/Heinzelschelm)\ **Post date:** [September 20, 2024, 5:49pm UTC](https://forum.storj.io/t/storagenode-stopped-working-on-pi4-error-the-certificate-of-version-storj-io-is-not-trusted/27976/3 "2024-09-20T17:49:50Z")
If I check in the linux shell with “date” it is displaying the correct date and time. Do I need to set it seperately for docker? ---
**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\ **Post date:** [September 20, 2024, 5:53pm UTC](https://forum.storj.io/t/storagenode-stopped-working-on-pi4-error-the-certificate-of-version-storj-io-is-not-trusted/27976/4 "2024-09-20T17:53:12Z")
> [@arrogantrabbit](#): > > Cannot get REALTIME clock frequency: Operation not permitted > **[docker: unknown syscalls return invalid \`EPERM\` (#11774) · Issues · alpine /...](https://gitlab.alpinelinux.org/alpine/aports/-/issues/11774)** > > This is exposed due to the upgrade to musl-1.2. When trying to execute the syscall clock\_gettime64, docker returns EPERM, instead of the expected ENOSYS. Because this unexpected return... You can workaround it by adding `--privileged` to the docker run command ---
**Author:** ![Heinzelschelm](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/heinzelschelm/32/1138_2.png) [@Heinzelschelm](https://forum.storj.io/u/Heinzelschelm)\ **Post date:** [September 20, 2024, 6:00pm UTC](https://forum.storj.io/t/storagenode-stopped-working-on-pi4-error-the-certificate-of-version-storj-io-is-not-trusted/27976/5 "2024-09-20T18:00:27Z")
That did work! Thanks a lot ---
**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\ **Post date:** [September 20, 2024, 6:06pm UTC](https://forum.storj.io/t/storagenode-stopped-working-on-pi4-error-the-certificate-of-version-storj-io-is-not-trusted/27976/6 "2024-09-20T18:06:29Z")
BTW I’d suggest considering getting away from docker. [Podman](https://podman.io) is lightweight, containers can be managed by systemctl, with all the features like auto-update and namespaces, and what not. Especially on a raspberry pi I’d think the resource conservation shall be important. I have summarized how to run rootless containers in podman here: [Running auto-updatable services in rootless containers with podman on Oracle Linux/RHEL/Fedora with SELinux enabled | Trinkets, Odds, and Ends](https://blog.arrogantrabbit.com/net/podman/) ---
**Author:** ![corkills](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/corkills/32/1138_2.png) [@corkills](https://forum.storj.io/u/corkills)\ **Post date:** [September 22, 2024, 4:54pm UTC](https://forum.storj.io/t/storagenode-stopped-working-on-pi4-error-the-certificate-of-version-storj-io-is-not-trusted/27976/7 "2024-09-22T16:54:26Z")
Are there any other solutions to this? Stopping/removing the container and then restarting with `--priviledged` makes no difference. I still get the same error shown in the start of the logs. This is also on an Pi4. ---
**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\ **Post date:** [September 22, 2024, 7:12pm UTC](https://forum.storj.io/t/storagenode-stopped-working-on-pi4-error-the-certificate-of-version-storj-io-is-not-trusted/27976/8 "2024-09-22T19:12:59Z")
Where in the command line do you add the flag? Show the full command. ---
**Author:** ![corkills](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/corkills/32/1138_2.png) [@corkills](https://forum.storj.io/u/corkills)\ **Post date:** [September 22, 2024, 7:44pm UTC](https://forum.storj.io/t/storagenode-stopped-working-on-pi4-error-the-certificate-of-version-storj-io-is-not-trusted/27976/9 "2024-09-22T19:44:22Z")
Ah, I does work, I had two problems: 1. I can’t spell - I’d added an extra `d` to `--privileged` 2. I’d put it last, putting it before the `--mount` and `--name` flags made it work I’m back up and running, thanks for your help 🙂