Closed cxaqhq closed 2 years ago
Hello @cxaqhq,
Could you give me some details about your environment?
Are you running from a docker instance or a local development?
If you are running from code, what is your operating system? The only supported OS to run the server is Linux currently.
I added now a logger wich probably will give some details about the error on the terminal. So if you running from a local development just update your branch and get the last changes.
root@VM-4-7-debian:~# uname -a Linux VM-4-7-debian 4.19.0-11-amd64 #1 SMP Debian 4.19.146-1 (2020-09-17) x86_64 GNU/Linux
Docker is not used.
Could you try this test.
Run on your terminal inside the root project:
cd client
GO_ENABLED=1 GOOS=windows GOARCH=amd64 go build -o main.exe main.go
file main.exe
It should build a executable from the source code client, if occurs some error, probably we will see the reason.
The output should be something like this:
Probably your golang version is old than Go 1.16. Its a requirement to be >= 1.16, i didn't specify on readme.
To see your version run:
go version
You should update your golang version or run from a docker instance.
okok,Thank you for your guidance
It can now be generated, but it was killed by WindowsDefender. Can I modify the client source bypassAV?
Unfortunately we don't have currently a bypass built in functionality, on the future versions probably we are work on it.
So you should use a third party project to do that.
304? run exe not Connected Devices
http 304 is just the browser cache downloading the Web UI js.
The machine running the client have access to your server? check if IP and port are correct.
IP prot is correct
I added some logs on client when connecting with server, probably now you can see some error. You need to get the latest code from repository.
Could you try it? Sorry for delay.