I was trying to selfhost jitsi meet (used for video conferencing) through my raspberry pi 4
I have followed this tutorial
Now, when I try to open my domain (I've got it from no-ip) it takes too long then shows this error: ERR_CONNECTION_TIMED_OUT
In a video I watched they say wait a few minutes for the domain to propagate
I have waited for 30 minutes and its not up yet, have I waited long enough? if yes, does that mean something else is wrong? what could it be?
Thanks in advance
okay its over
just don't believe anyone who tells you to close port 80 after downloading the keys
open ports: 80, 443,4443, 10000
Related
Hello everyone how are you, it happens that when the video call is in progress, sometimes the video is delayed with respect to the audio, and it is never re-adjusted (unless you refresh the page).
-I have ports 80 and 443 enabled
-I don't have a firewall in between
-I don't have any proxy
-The server never has more than 2 sessions and each one has no more than 12 participants
What advice or solutions can you give me in this case? Thanks in advance.
I know that this question has been asked in multiple forums and have several versions of the answers.. Unfortunately, none of those answers helped me out to resolve my issue.
I stood up an AWS EC2 instance of Windows Server 2016 and installed IIS, MSMQ, Windows Process Activation Service and few other things.. When I cracked open my IIS Manager, I noticed that the "Default Web Site" is stopped and when I tried to start it I get an error "The process cannot access the file because it is being used by another process (Exception from HRESULT:0x80070020)". Tried to dig a little more and found these two exceptions in my Event Viewer:
Unable to bind to the underlying transport for [::]:80. The IP Listen-Only list may contain a reference to an interface which may not exist on this machine. The data field contains the error number.
The World Wide Web Publishing Service (WWW Service) did not register the URL prefix http://:80/SmsHandler for site 1. The site has been disabled. The data field contains the error number.*
Researching more online I found more than 2 dozen articles on this issue and more than 95% of them saying that the potential application that might be conflicting with IIS and using port 80 and 443 could be Skype.. But I DON'T HAVE SKYPE installed on my server..
I ran the "netstat -aon" command and found this:
C:\Windows\system32>netstat -aon | findstr :80
TCP 169.254.170.2:80 0.0.0.0:0 LISTENING 1164
Going by what's mentioned in other articles online.. I tried to trace down the PID - 1164 in my Task Manager and found that its the "Service Host - Local System" process having 15 System services running into it.. There's no way I can kill that process to make my IIS work..
I then tried to change the Bindings in my IIS to listen on a different port than 80 and was able to get it up and running.. But I don't want IIS to run on any other port than 80 since I don't want the user to specify the port in the URL every time when they hit the website..
I'm now running short of ideas here.. Any suggestions would be greatly appreciated.
Thanks!
I ran into a similar issue, but not with port 80. In my case it was because the ip address [::] wasn't allowed to listen on any port. Adding it to the ListenOnly list in the registry fixed the issue.
From an admin command prompt:
netsh http add iplisten ipaddress=::
From this thread.
Found the culprit.. It apparently wasn't skype for me (as it is in most of the cases), it was this service called IP Helper which was running on port 80 and was conflicting with IIS. The way I found that out was, I checked all the services running under the PID for Service Host - Local System (which in my case as 1164) and started stopping them one at a time and saw if IIS starts working.. Just wanted to close this thread.. Hope this helps if someone else get stuck with the same issue.
I had VMware Workstation installed, the solution is: "VMware -> Edit -> Preferences -> Shared VMs -> "Disable Sharing".
I have a NodeJS server deployed with ExpressJS and the thing is that when I access it from computers in the same LAN works very well, but when I try to reach the server from outside, I have to wait almost 20 seconds to get all the data.
Any clues?
Thanks in advance!
I'm using Socket.IO on Node.js.
The Example here: http://socket.io/#how-to-use
First Example.
I have tested on my computer, it works great. ( Installed on VPS, connect by IP. not localhost )
But the problem is, my friends, they visit the page:
http://112.78.8.221:8085/
Press F12 for debug , under Console, they show not thing.
But in my browser console ( Chrome, Firefox ) , I see a object return.
On debug of my friend:
I see :
jsonppolling closed due to exceeded duration
setting request GET /socket.io/1/jsonp-polling/blablabalblabal
Setting poll timeout
discatding transport and same as xhr-polling, timeout and discard.
So, both of us used latest version of Chrome and FF, can u guys help on this one? a week with this problem already :(
I believe there is something strange going on with his network. Maybe he is going through a proxy connection or something? I was able to hit your service and got an object back without a problem. Some offices and universities will also block ports other than the common 80, 443, 22, etc. If you can, try hosting on a lower port number, or if possible on port 80 to eliminate that as a cause of the problem.
While profiling my application I've noticed that in the Firebug Net panel, the "Connecting" time—that is the time waiting for a TCP connection—is consistently around 70–100ms. See image below:
Of course in the grand scheme of things, 100ms is not long, but I have seen other services that respond with 0ms Connect time. So if other servers can, I should be able to as well.
Any thoughts on how I might even beging to troubleshoot this?
I would start with looking to see if iptables is doing anything that may get in the way. Also, if you were working with an ELB load balancer, (or any other load balancing), I'd remove it from the mix and see if you are still having the longer than expected connect time.
You could also separately install lighttpd or Apache and see what happens. If you get a lower connect time, than that would point to your Node.js build. Although not definitively.
I would suggest a simple test to check if this problem is related to your server:
Launch another instance in the same availability zone as your server.
Benchmark your server with Apache Benchmark from the second instance:
ab -c 1 -n 20000 http://<private_server_instance_ip>:<port>/<URL>
It is important to put private IP here, not private or public DNS to sweep aside domain name resolution effects.
Check the average time taken per request: If it will be around 1 ms - the problem described is not of your server.
Benchmarking with FireFox BTW may not be the best idea because the results might depend on a number of circumstances.