The issue with running on VPS

[Leneneq]

When launching the bot on a virtual server (VPS), a white screen (Attachment 11.png) appears where nothing can be opened, as if the terminal is frozen (the File, Actions, Options, Help tabs cannot be clicked).

Before starting, the following message appears:
"Open ERROR: Can not open the file as [zip] archive

ERRORS:
Is not archive"

The error occurs regardless of the SSH connection via Putty or Tabby.

Machine: Ubuntu 22.04.4 LTS
dotnet: 6.0.127

[sussyjelou]

I'm not sure if the buttons are intended to be clickable. I'm using this console version on Raspberry OS and I control the bot using ALT + the first yellow letter. I think it should work for you too.

[jsfrz]

If you want to run MFbot on VPS, I would recommand using Docker. Create folder for the project and create Dockerfile:

Code: Alles auswählen

FROM alpine:latest

RUN apk --no-cache add wget dotnet6-runtime libc6-compat screen bash

WORKDIR /app

COPY Acc.ini .

RUN wget https://download.mfbot.de/nightly/MFBot_Konsole_x86_64

RUN chmod +x MFBot_Konsole_x86_64

RUN mkdir -p ~/.local/share/mfbot.de/
RUN mkdir -p ~/.config/mfbot.de

CMD ["sh", "-c", "screen -S MFBotSession -d -m ./MFBot_Konsole_x86_64 && tail -f /dev/null"]

Now place your Acc.ini in the folder and run this to build the image and start the bot:

Code: Alles auswählen

sudo docker build -t mfbot .
sudo docker run -d --restart always --name mfbot mfbot

You wont be able to interact with it, but you can always use Portainer or command to stop the container. I have tested this on Debain 12 with no desktop environment. What Dockerfile does is just downloading latest nightly build and creating image from it.

[frank42]

While docker is a possible solution, I would suggest something not that overbloated...

I run the bot with -l within a screen¹ session. Works perfectly and has almost no overhead at all.

1) https://www.gnu.org/software/screen/man ... l#Overview