Remote Access

[Jonas.Sellmann@outlook.de]

Jonas, I don't know if you would provide too much internal and intellectual information ... but is it possible that we can get the three containers to us? So then we can start an evaluation of all three containers here and make a long term test. Or do those containers need a special external hardware to run?

No, unfortunately we can't do that. Moreover for the communication, the container need speacial bluetooth devices, we are developing.

---

I can still access the bluetooth container with ssh, but always I try to use a command either there comes up "input/output error" or there comes up "command not found".

I just want to understand the three containes a little closer. We share the opinion that in no way any container ever should cause netPI to stop normal operation respectively cause "bad gateway" for its web interface.

So you log in to your netPI via openVPN container ... and over this connection you can reach the bluetooth container via ssh and open a terminal. Is my understanding correct?

And then if you call in this terminal a standard linix console command like "dir" or "ls" or "apt-get" or anything else you get the "input/output error" or command not found, right?

Yes, thats exactly what I'm doing. Yes standard linux commands does not work.

---

What is if your try to access netPI with https://<ip address netpi>/portainer? Does it work?

Unfortunately i tried this description to restart the netPi with the terminal of the conatiner: https://matoski.com/article/emergency-re...nux-sysrq/

The netPi was shut down, but does not restart and isn't accessible anymore.

Tomorrow we have a chance get access to the hardware, so maybe we can fix the errors.

But in the future we need a system that we can manage from remote, when there are errors, because we don't always have the chance to go to our customers.

Isn't there a chance to get access to the linux system of the host system?