search

Misioslav / expressvpn

51 stars 25 forks source link

service expressvpn restart failed ! #39

Open Ghazzawi76 opened 5 months ago

Ghazzawi76 commented 5 months ago

Hi I need your help ...

I am running CasaOS on raspberry pi 5 , docker version 26 ,,, i am unable to get the expressvpn to work ..

i use the command below and keep getting either the container "exited" or it runs healthy but in the logs keep saying " service expressvpn restart failed !"

docker run --env=WHITELIST_DNS=192.168.1.1,1.1.1.1,8.8.8.8 --env=CODE=MyExpressvpnActivationCode --env=SERVER=smart --cap-add=NET_ADMIN --device=/dev/net/tun --privileged --detach=true --tty=true --name=expressvpn --publish 80:80 --env=PROTOCOL=lightway_udp misioslav/expressvpn:latest-bookworm /bin/bash

i tried many images like

misioslav/expressvpn:latest-bookworm
expressvpn:latest-bookworm

and the older images

Misioslav commented 5 months ago

Hey,

Please, try to run it like this:

    docker run \
    --env=CODE=MyExpressvpnActivationCode \
    --env=SERVER=smart \
    --cap-add=NET_ADMIN \
    --device=/dev/net/tun \
    --privileged \
    --detach=true \
    --tty=true \
    --name=expressvpn \
    misioslav/expressvpn:latest \
    /bin/bash

Why MyExpressvpnActivationCode is of course filled with your code from ExpressVPN subscription.

Ghazzawi76 commented 5 months ago

first i never had a chance to thank you for all your work dear ..

i tried the command above but got this error

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested

shall i try

misioslav/expressvpn:latest-bookworm

Misioslav commented 5 months ago

ah, true, you are on rb 5, you can try with :latest-arm64 or :latest-armhf. :latest-bookworm may potentially also work

Ghazzawi76 commented 5 months ago

:latest-arm64 or :. :latest-bookworm does NOT work ...

i will try latest-armhf now

Misioslav commented 5 months ago

Are you getting the same error? If you can, please, post here the logs you are seeing either as image or as copy paste text.

Ghazzawi76 commented 5 months ago

Thank you for your patience ,,, only armhf gave me healthy status but it does not connect 1 2

Ghazzawi76 commented 5 months ago

maybe i should publish it on port 80 and retry ?

Ghazzawi76 commented 5 months ago

nope ===> even when i add --publish 80:80 \ i still get the same error

root@CasaOS:~# docker logs expressvpn Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed!

Misioslav commented 5 months ago

Port 80 might be taken by the system resources so it might not be the best to try to reserve it.

Can you show/copy the logs from portainer view?

But it's interesting. I've just tried it locally and the following works for me like a charm:

docker run -i \
    --env=CODE={{CODE}} \
    --env=SERVER=smart \
    --env=AUTO_UPDATE=on \
    --cap-add=NET_ADMIN \
    --device=/dev/net/tun \
    --privileged \
    --detach=true \
    --tty=true \
    --name=expressvpn \
    misioslav/expressvpn:latest-bookworm \
    /bin/bash
Ghazzawi76 commented 5 months ago

unfortunately cannot share pertainer view because there is known compatibility issue between portainer and docker 26

https://www.portainer.io/blog/portainer-and-docker-26

i will give your command above another shot

Ghazzawi76 commented 5 months ago

same now this image says "existed"

Ghazzawi76 commented 5 months ago

can i ask you if you are running this on a RSPi 5 ?

Misioslav commented 5 months ago

https://www.portainer.io/blog/portainer-and-docker-26

So I assume logs view also stopped working with docker 26 in portainer?

can i ask you if you are running this on a RSPi 5 ?

I do not own Raspberry Pi currently, so Im testing it locally on my Mac and Synology NAS. On my MAC I have Docker in version 26.0.0 and on NAS Docker 25.0.3.

Maybe due to architecture differences something is not starting or working like in it's desktop equivalent. Although, my MAC is M1 so it has ARM architecture tho.

Ghazzawi76 commented 5 months ago

i just want to let you know that i have also a RSPi 4 and it is running the image below like a charm

misioslav/expressvpn:latest-arm64-bullseye

i just struggling with this RSPi 5

Misioslav commented 5 months ago

i just want to let you know that i have also a RSPi 4 and it is running the image below like a charm

misioslav/expressvpn:latest-arm64-bullseye

and you are using the same OS on RSPi4 that you have on RSPi5? Maybe there are differences that Im currently not aware of and maybe a specialized image for RSPi5 might be needed 🤔

Ghazzawi76 commented 5 months ago

I used the same OS ( OpenMediaVault) and had similar issues

now i switched to CasaOS thinking that this will solve the issue with no luck

i just got the Rspi 5 and setting it us as a home server

please see what you can do and save the day :)

Misioslav commented 5 months ago

I used the same OS ( OpenMediaVault) and had similar issues

now i switched to CasaOS thinking that this will solve the issue with no luck

i just got the Rspi 5 and setting it us as a home server

please see what you can do and save the day :)

If you could test it on your side https://forums.raspberrypi.com/viewtopic.php?t=360071

Ghazzawi76 commented 5 months ago

i will try it now

Ghazzawi76 commented 5 months ago

Same results even with 6.6.20+rpt-rpi-2712

Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! root@CasaOS:~# uname -r 6.6.20+rpt-rpi-2712

Ghazzawi76 commented 5 months ago

i will try now to install a different OS

Openmediavault and try again the whole process

Ghazzawi76 commented 5 months ago

in the meanwhile please try to see if you can create an image for RSPi5

Ghazzawi76 commented 5 months ago

i have to tell you dear that even with OMV7 the issues are exactly the same

we need your help with a working image

Misioslav commented 5 months ago

i have to tell you dear that even with OMV7 the issues are exactly the same

we need your help with a working image

It will be impossible for me to debug it at this stage as I do not have Raspberry Pi 5 and it works on everything else at this stage. I assume the issue with Service expressvpn restart failed! is that it didn't even start so it can't be restarted. It could not have started for many reasons related to Raspberry Pi architecture or anything else.

You can try to start the service manually via docker excec command for the docker like service expressvpn start and see what errors will it return (if any). Maybe such information will allow us to move forward somehow.

Ghazzawi76 commented 5 months ago

3 sorry to trouble you with this ... here is the command output of the docker exec

root@OMV7:~# docker exec 9556888af837 service expressvpn restart Restarting ExpressVPN service: expressvpnd/etc/init.d/expressvpn: line 111: 38389 Segmentation fault nohup start-stop-daemon --start --quiet -m --pidfile "$PIDFILE" --exec "$DAEMON" -- "${DAEMON_ARGS[@]}" >> "$STDOUT" 2>> "$STDERR" failed! root@OMV7:~#

Misioslav commented 5 months ago

Can you run also service expressvpn start and as next command bash /expressvpn/start.sh

Both will return errors most probably, but let's see if those errors will give us more information.

Ghazzawi76 commented 5 months ago

done dear .. please see below and attached

root@a83096f88ffb:/# bash /expressvpn/activate.exp
/expressvpn/activate.exp: line 5: spawn: command not found /expressvpn/activate.exp: line 6: match_max: command not found couldn't read file "{": no such file or directory /expressvpn/activate.exp: line 8: Already activated. Logout from your account (y/N)?: No such file or directory /expressvpn/activate.exp: line 9: send: command not found /expressvpn/activate.exp: line 10: syntax error near unexpected token }' /expressvpn/activate.exp: line 10: }' root@a83096f88ffb:/#

root@a83096f88ffb:/# service expressvpn start Starting ExpressVPN service: expressvpnd/etc/init.d/expressvpn: line 111: 6804 Segmentation fault nohup start-stop-daemon --start --quiet -m --pidfile "$PIDFILE" --exec "$DAEMON" -- "${DAEMON_ARGS[@]}" >> "$STDOUT" 2>> "$STDERR" root@a83096f88ffb:/# root@a83096f88ffb:/# root@a83096f88ffb:/# bash /expressvpn/start.sh Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! Service expressvpn restart failed! ^C root@a83096f88ffb:/# 4

Misioslav commented 5 months ago

Thank you, I will try to research the topic a bit more in the upcoming days.

ItsTheSeabass commented 5 months ago

Are there any updates for RP5 yet? when i try to just run it on docker it says exited in red

Misioslav commented 5 months ago

Unfortunately, I do not have how to test any potential solution I can come up with for now. Ive prepared some changes for the build if you want to you can check If it works for you

misioslav/expressvpn:rpi5-experimental

ItsTheSeabass commented 4 months ago

Service expressvpn restart failed!

This is the only thing in the logs.

unable to retrieve image details when i click on terminal

Container shows 'Healthy' status

firefox_Ls9j082wX3 firefox_rWS1gBP3ZD firefox_WWk6oCmZas

Misioslav commented 4 months ago

I will try keep digging when I have a moment but if you know a working image for expressvpn on rpi5 please let me know. I will take a look at that as well.

Webreaper commented 4 months ago

Seeing this on my synology again. It was all working until about a couple of weeks ago.

Misioslav commented 4 months ago

Seeing this on my synology again. It was all working until about a couple of weeks ago.

This issue is related to rpi5 so if need be please open a new issue. But as you can see not much have changed in recent weeks in the container. And nothing really in the start up procedure was touched. I did not observe this behavior since last fix on my synology. You can check older versions if those are causing the same issue.

Webreaper commented 4 months ago

Okay. Seems weird. I tried the script fix that normally solves it, but no joy. Will fiddle and open another issue if I can't get it to work.