How to restart crashed HTTPD server and Transmission?

[Cubytus]

Same error on Vivaldi, BTW. So probably not linked to FF

[Jocko]

Hi

When you try to install an addon package, error code -99 means the firmware failed to get a session with your plugout credentials (or failed to detect a new user session is available).

So first check your login, run

Code: Select all

plugout check
echo $?

You should get the value 0. You can confirm that by reading the cookie file

Code: Select all

cat /tmp/cookie.txt

You should have a line

Code: Select all

#HttpOnly_.plugout.net  TRUE    /       FALSE   1777448743      phpbb3_hy4o6_u  YYYY

where YYYY is your user id; If YYYY is equal to 1 that means your credentials are wrong. In this case you have to enter them again (setup menu, tab Firmware interface)

if you get your user id, maybe the firmware fails to detect the user session id. So do

Code: Select all

plugout download 7253

post the output and also

Code: Select all

cat /tmp/headers.txt

(maybe you do not have the expected headers. This may happen with some ISP)

[Cubytus]

Hi Jocko,

Your login fault hypothesis was correct:

Code: Select all

# plugout download 7253
Can not login!


I corrected as you said and now got:

$matches[2]

On FF, I noticed that I changed the password about a year ago :oops: . Since I had a very long uptime and don't change the interface very often, that's probably why the stored password wasn't valid anymore

Now for the following steps:

Code: Select all

# plugout check

Code: Select all

# echo $?
127


Code: Select all

# cat /tmp/cookie.txt
# Netscape HTTP Cookie File
# https://curl.se/docs/http-cookies.html
# This file was generated by libcurl! Edit at your own risk.

#HttpOnly_.plugout.net   TRUE   /   FALSE   1777470055   phpbb3_hy4o6_sid   abcde5167185875676
#HttpOnly_.plugout.net   TRUE   /   FALSE   1777470055   phpbb3_hy4o6_k   
#HttpOnly_.plugout.net   TRUE   /   FALSE   1777470055   phpbb3_hy4o6_u   6731

Code: Select all

# plugout download 7253
login successful
file='/tmp/addon-syncthing-arm-1.27-18mar2024.tgz'
logout successful


However, nothing appears with [pre]cat /tmp/headers.txt[/pre], file just doesn't exist.

Since you provided the example of downloading the syncthing add-on, this was only the first part of the process, aKa downloading the addon, but not install it yet, so this would be correct?

Captura de Pantalla 2025-04-29 a la(s) 09.46.17 .png

[Jocko]

Hi

So that seems good :thumbup Can you start now transmission ?

However, nothing appears with [pre]cat /tmp/headers.txt[/pre], file just doesn't exist.

if you run another plugout command (for example to check your credentials), this file is deleted. But it it is useless as now the firmware can manage a plugout session with your credentials.

Since you provided the example of downloading the syncthing add-on, this was only the first part of the process, aKa downloading the addon, but not install it yet, so this would be correct?

Yes it is correct


There is only one point I do not understand why you got the value 127 on stderr after checking your credentials (or it was before updating them ?)

[Cubytus]

Yes it works now. Transmission is running smoothly now :woohoo

No clue about error 127 though…

A few remaining errors though…
It still can't connect to my No-IP account to update. On the account, 2FA is enabled, and there's no obvious way to use an app password.
fvdw-sl does act as an NFS server, and I vaguely remember there was also a way to turn it as a client to a NFS server, except that it's not in the GUI, and the forum search engine ignores 3-letters words.
AFP sharing still randomly disconnects
LED never lights up. On boot it briefly flashes, but doesn't stay on. Oh well.

Suggestion:
as rclone seems to be working, maybe add a GUI pane or make it an official add-on?

[Cubytus]

Hmm, another one I just found:
The NAS has rebooted last morning, and I can't find out why.

How do I check that?

Code: Select all

/var/log/messages

is empty (o bytes)
I already ruled out disk temperature, as it is configured to sleep for 30 minutes and it's not warm enough anyway.

[fvdw]

that may happen if you have had a power failure.
When the kernel or a program crashes the nas won't reboot but halt or log an oops message in the dmesg output.

[Cubytus]

You know what…
I think you were right. :hail
I took advantage of the downtime to plug the NAS on one of those DC UPSes and naively used the included dual-head 12V lead to power both the router and the NAS. Being low-cost, there is no serial or USB communication.

Turns out the power from the UPS, even at 12V@2A, sometimes wasn't enough for both devices, and the UPS just cut the power, even for a very brief amount of time. The uptime was the same on both the NAS and the router, and the only common denominator between those was the UPS.

I now have isolated the router on a smaller DC UPS, and so far, no unexpected shut-down occurred.

Any idea how to have a No-IP account updating?