plz i need help WebSocket does not appear to be live

[live-industrial]

i have try to install it in my aws ubuntu but after i install the extention no connection

[live-industrial]

can any one help me with this problem WebSocket does not appear to be live! Restarting the WebSocket connection...

[live-industrial]

[jemieukgoi]

i have same problem did you find the solution ?

[live-industrial]

@mandatoryprogrammer can you plz anser me this will help me a lot in my work

[Matir]

If you're going to use DNAT you probably need to set net.ipv4.conf.all.route_localnet so that the kernel doesn't drop the packet on the incoming interface. Note that this has security implications -- anything on your LAN can now potentially inject packets that pretend to be local packets.

[jemieukgoi]

@mandatoryprogrammer can you plz anser me this will help me a lot in my work don't waste your time for this project will not work

[mandatoryprogrammer]

@jemieukgoi let me be clear, you are not entitled to free IT support just because this is an open source project. Replying this way after @Matir went out of his way to help you is embarrassing. It also does not make me want to help you. The maintainers of this project have full time jobs and limited free time outside of them. They don't have to spend them helping out on Github issues. You are always free to write your own version of CursedChrome if you have having problems setting this up.

As far as I can tell, I don't see any nginx setup in what either of you posted. You need to have HTTPS for this to work, and nginx + LetsEncrypt is the easiest way to do this. You can't use the server directly to host the websockets. This is mentioned in the comments of the screenshot posted originally in this thread. There are also free videos that walk you through how to set it up: https://www.youtube.com/watch?v=cdSXdwa5trc

[live-industrial]

@mandatoryprogrammer thanks

[bhatritesh]

@mandatoryprogrammer can you plz anser me this will help me a lot in my work don't waste your time for this project will not work

@jemieukgoi No need to act like a clown. People are helping you in an open source project and you decide to act like this. Nonce!

@live-industrial it's a networking issue. Here's how I fixed it:

• Ensure that packet forwarding is enabled on your attacker machine. You can do this by editing the sysctl configuration:
  echo 1 > /proc/sys/net/ipv4/ip_forward
• To make this change permanent, you can add the following line to /etc/sysctl.conf
net.ipv4.ip_forward = 1
• sysctl -p to apply the changes
• Set up iptables rules

# Flush NAT table to avoid conflicts
iptables -t nat -F

# Forward incoming requests on port 4343 to the Docker container
iptables -t nat -A PREROUTING -p tcp --dport 4343 -j DNAT --to-destination 172.17.0.X:4343

# Allow forwarding of packets to the Docker container
iptables -A FORWARD -p tcp -d 172.17.0.X --dport 4343 -j ACCEPT

• Replace 172.17.0.X with the actual IP address of the Docker container, which you can find by running below:
  docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' <container_name_or_id>