Connect error

[Miku-nya]

Connection error.
I run this script on the ubuntu 20.04 system and run the script, it generated the necessary data for the vless connection and gr code, but when I connect to my server via nekobox (windows 10) it gives an error:
create service: parse outbund[0]: invalid public_key
How to fix this error?

[saliei]

Ok, for some reason, xray doesn't register the private and public key, generated inside a script, have to do it manually, use the temple config inside the configs directory, and then generate the uuid, with: ./xray uuid, private&public key with: ./xray x25519, and the shortId with: openssl rand -hex 4, then plug this info in the respective fields inside the template config and then start the server with ./xray run --config <path-to-filled-config.json>, in my experiments it's better to just download the latest xray-core (>=v1.8.0) release from their repo and copy the binary to current dir. will investigate this issue to see if there's a possible way to generate them ids.

[Miku-nya]

I somehow managed to get started, thanks for the help. Now there was a problem with the fact that outgoing traffic does not pass. It only shows the statistics of incoming traffic, the command with windows (I use necobox) through a domain ping (for example, google.com) does not work.
I tried to connect on android 10 (nekobox) via mobile Internet and traffic is not shown there at all.
The acess.log file also appeared in the folder with the script, and errors are pouring in there when connecting from Windows:
2023/04/22 14:14:53 my ip adress:7882 rejected proxy/vless/encoding: invalid request user id
2023/04/22 14:14:53 my ip adress:7883 rejected proxy/vless/encoding: invalid request user id (port changes every time by +1)

[Miku-nya]

reopen

[saliei]

I see, I would suggest making sure that you can ping the IP of the server, you can use a service like check-host, if it can't be pinged, you can check the firewall of the VPS, the ICMP protocol must be open. If all is well, try grabbing another template configuration, and make sure that the camouflage website can be accessed from the location of the server.

FYI: the issue with the script is fixed, now it can be used normally.