500 - Server Error when adding one specific link

[mmozzano]

Describe the bug
A clear and concise description of what the bug is.
Getting an error stating:
500 - Server Error
An internal server error occured. If you are the administrator, consult the application logs for details.

When attempting to add link:
https://www.grc.com/passwords.htm

Have tried Quick Add and Add via Firefox extension with same result.

To Reproduce
Steps to reproduce the behavior:

1. Go to main screen, in Quick Add Link enter 'https://www.grc.com/passwords.htm'
2. Click on Add button
3. See error: 500 - Server Error
   An internal server error occured. If you are the administrator, consult the application logs for details.

In docker log I see the following:

127.0.0.1 - 02/Mar/2022:21:04:05 +0000 "POST /index.php" 500
172.20.0.4 - - [02/Mar/2022:21:04:07 +0000] "POST /links HTTP/1.1" 500 5456 "https://linkace.local.REDACTED.co.uk/dashboard" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:97.0) Gecko/20100101 Firefox/97.0" "192.168.1.98"

Expected behavior
Link should add correctly, dont have an issue adding another other links.

Screenshots
NA

LinkAce setup (please complete the following information):

• Version:1.9.1
• Installed via:Docker Simple
• OS: Raspbian GNU/Linux 11 (bullseye)

Desktop (please complete the following information if applicable):

• OS:Windows 10
• Browser Firefox
• Version 97.0.1

Additional context
NA

[Kovah]

What about the system logs, which are accessible from the menu?

[mmozzano]

Hi, thanks for the respose.

The message in the system log is:

strtotime(): Epoch doesn't fit in a PHP integer {"userId":1,"exception":"[object] (ErrorException(code: 0): strtotime(): Epoch doesn't fit in a PHP integer at /app/vendor/guzzlehttp/guzzle/src/Cookie/SetCookie.php:255)

[Kovah]

See #365

[mmozzano]

Interesting, I'm on bullseye:

PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)"
NAME="Raspbian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=raspbian
ID_LIKE=debian

Ran the following:

sudo dpkg -i libseccomp2_2.5.1-1+deb11u1_armhf.deb            (Reading database ... 100934 files and directories currently installed.)
Preparing to unpack libseccomp2_2.5.1-1+deb11u1_armhf.deb ...
Unpacking libseccomp2:armhf (2.5.1-1+deb11u1) over (2.5.1-1~bpo10+1) ...
Setting up libseccomp2:armhf (2.5.1-1+deb11u1) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u2) ...

Restarted linkace container and still getting the same error. I've also restart the docker service with the same issue still happening.

[mmozzano]

I am on 32bit. Are you saying I should be looking at upgrading to 64 bit?

[Kovah]

Did you try to restart the device?

Otherwise I can't help if upgrading to libseccomp 2.5 does not solve the issue. I have no 32-but devices at hands.
You may be able to find further help by searching for the error message. I found the hint for libseccomp while doing the same.

Edit: please let me know if you found a fix and I will add it to the FAQ entry.

[mmozzano]

Thanks for the response. Yes I'll I've tried stopping the container, docker and the device itself. I've also found another later version of libseccomp (libseccomp2_2.5.3-2_armhf.deb) which also doesn't work.

I've ordered another drive so I'm going to image a 64 bit system as it was something I was keen to do anyway so I'll let you know how I get on in the next day or so once the drive arrives.

[mmozzano]

A quick update - I've reimaged my Pi4 with 64 bit Raspberry Pi OS and re-deployed all my Docker containers. This issue has now gone away and I'm able to add the link without any issues.

Out of interest I had a look what version ships out of the box with 64 bit OS:

dpkg -s libseccomp2 | grep '^Version:'
Version: 2.5.1-1+deb11u1

This is the same version of libseccomp2 I tried on 32bit OS so I suspect there is something else causing the issue and simply upgrading to a newer version on 32bit isnt always a fix.

Anyway, thanks for your help and love LinkAce :)

[Kovah]

Thanks for taking the time to upgrade your OS just for LinkAce! 😊
Good to hear everything works now. Who knows what the exect issue was.