12-03-2023, 12:54 AM
(12-03-2023, 12:44 AM)hurcheon Wrote:(12-01-2023, 02:52 PM)TheOldPresbyope Wrote: PS
From a Linux command line, at least, it's easy to get details about the connectivity to the moOde streaming server using curl.
Hi
Thanks for this
Tried from both Windows and Linux, this is the Windows output because this where I was looking at the forum
Code:C:\Users\winuser> curl -v -o NUL http://192.168.1.236
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 192.168.1.236:80...
* Connected to 192.168.1.236 (192.168.1.236) port 80
> GET / HTTP/1.1
> Host: 192.168.1.236
> User-Agent: curl/8.4.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx/1.18.0
< Date: Sun, 03 Dec 2023 00:39:08 GMT
< Content-Type: text/html; charset=UTF-8
< Transfer-Encoding: chunked
< Connection: keep-alive
< Set-Cookie: PHPSESSID=ho7vk67sqrjua8sme0pqhsjgdq; path=/
< Expires: Thu, 19 Nov 1981 08:52:00 GMT
< Cache-Control: no-store, no-cache, must-revalidate
< Pragma: no-cache
<
{ [1122 bytes data]
100 158k 0 158k 0 0 2261k 0 --:--:-- --:--:-- --:--:-- 2263k
* Connection #0 to host 192.168.1.236 left intact
C:\Users\winuser> curl -v -o NUL http://192.168.1.236:8000
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 192.168.1.236:8000...
0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0* connect to 192.168.1.236 port 8000 failed: Connection refused
* Failed to connect to 192.168.1.236 port 8000 after 2075 ms: Couldn't connect to server
0 0 0 0 0 0 0 0 --:--:-- 0:00:02 --:--:-- 0
* Closing connection
curl: (7) Failed to connect to 192.168.1.236 port 8000 after 2075 ms: Couldn't connect to server
Interestingly, this time, Windows still refuses to resolve the domain, but Linux gets it by alias, the phone won't take either
All on the same network, weird
Well, actually this was a check of connectivity to the default port 80 (which is the WebUI interface) rather than port 8000.
What about Tim's observation about breakage in the audio config?
Regards,
Kent