-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connects OK but no stream #16
Comments
Does the My guess right now is that |
No. The returning image is empty (also double checked wget - resulting file is empty) |
curl --raw -v http://timemelter.com:54321/stream
|
Ok, give https://github.com/Silex/mjpeg-relay/tree/chunked-encoding-support a try and report. Btw, in your above paste after the headers there's nothing? My commit is based on http://docs.python-requests.org/en/master/user/advanced/#chunk-encoded-requests |
andre@rs209835:~$ git clone
https://github.com/Silex/mjpeg-relay/tree/chunked-encoding-support
Cloning into 'chunked-encoding-support'...
error: The requested URL returned error: 403 while accessing
https://github.com/Silex/mjpeg-relay/tree/chunked-encoding-support/info/refs
fatal: HTTP request failed
To your question: No. I assume it will run into a timeout eventually
…On 07.03.2017 22:47, Philippe Vaucher wrote:
Give
https://github.com/Silex/mjpeg-relay/tree/chunked-encoding-support a
try and report.
Btw, in your above paste after the headers there's nothing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZC178CqdwRT5z0hNc7joa0EaFhktsfLks5rjdBggaJpZM4MWCGv>.
--
André Stricker
Stricker Consulting
Lindenstrasse 45
D-35398 Gießen
Germany
Tel: +49 (0)641-33055205-0
Fax: +49 (0)641-33055205-9
Mob: +49 (0)179 29 43 130
e-Mail: [email protected]
www.scw-services.com
|
git clone git://github.com/Silex/mjpeg-relay
git checkout chunked-encoding-support |
Ah thanks. Done that. When I run the relay now, it looks ok again, but the /status page show no incoming bandwidth.. python relay.py -d -w 54018 http://admin:****@dyn-url:8091/mjpeg/stream.cgi?chn=1 mjpeg-relay status |
Please use a pastebin or use github's code blocks. Anyway, you are sure |
Hm. I just rebooted the camera and it didn't come up again. Camera is on
rooftop. I will have to double check tomorrow. I will get back. Sorry
for the delay and thanks for the support
…On 07.03.2017 23:11, Philippe Vaucher wrote:
Please use a pastebin or use github's code blocks.
Anyway, you are sure
***@***.***:8091/mjpeg/stream.cgi?chn=1| works
properly? Is it possible to setup some temporary viewer user for us to
use?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZC1724bEduve3V84rJKFwwnN88XEZgCks5rjdX-gaJpZM4MWCGv>.
--
André Stricker
Stricker Consulting
Lindenstrasse 45
D-35398 Gießen
Germany
Tel: +49 (0)641-33055205-0
Fax: +49 (0)641-33055205-9
Mob: +49 (0)179 29 43 130
e-Mail: [email protected]
www.scw-services.com
|
Here u go.
http://test:[email protected]:8091/mjpeg/stream.cgi?chn=1
I tried relaying this stream as well but no luck.
…On 07.03.2017 23:11, Philippe Vaucher wrote:
Please use a pastebin or use github's code blocks.
Anyway, you are sure
***@***.***:8091/mjpeg/stream.cgi?chn=1| works
properly? Is it possible to setup some temporary viewer user for us to
use?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZC1724bEduve3V84rJKFwwnN88XEZgCks5rjdX-gaJpZM4MWCGv>.
--
André Stricker
Stricker Consulting
Lindenstrasse 45
D-35398 Gießen
Germany
Tel: +49 (0)641-33055205-0
Fax: +49 (0)641-33055205-9
Mob: +49 (0)179 29 43 130
e-Mail: [email protected]
www.scw-services.com
|
Hello, Just had a quick attempt, looks like that gives a 401 even when connecting directly without using mjpeg-relay. Please check the credentials |
Camera is down again. Will climb up there tomorrow morning and get back.
Thanks already!
…On 08.03.2017 00:08, OliverF wrote:
Hello,
Just had a quick attempt, looks like that gives a 401 even when
connecting directly without using mjpeg-relay. Please check the
credentials
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AZC1758cc5Ai4l_KlSY4flH0vuIrn_9Fks5rjeNTgaJpZM4MWCGv>.
--
André Stricker
Stricker Consulting
Lindenstrasse 45
D-35398 Gießen
Germany
Tel: +49 (0)641-33055205-0
Fax: +49 (0)641-33055205-9
Mob: +49 (0)179 29 43 130
e-Mail: [email protected]
www.scw-services.com
|
The credentials are fine, you need to use digest auth. The problem is more like the camera only accepts very few connections... In all my attempts it only sent the MJPG once, and thus I could not debug. |
Hi,
I am trying to use the mjpeg-relay to relay a IP camera mjpeg stream. When launching the streamer, everything is looking fine. The terminal looks like this:
andre@rs209835:~/mjpeg-relay$ python relay.py -d -w 54018 http://admin:****@dyndns-host:8091/mjpeg/stream.cgi?chn=1
Starting new HTTP connection (1): dyndns-host
send: 'GET /mjpeg/stream.cgi?chn=1 HTTP/1.1\r\nHost: dyndns-host:8091\r\nAccept: /\r\nAccept-Encoding: gzip, deflate\r\nAuthorization: Basic YWRtaW46MTIzNDU2\r\nUser-Agent: python-requests/2.3.0 CPython/2.7.3 Linux/3.2.0-102-generic\r\n\r\n'
reply: 'HTTP/1.1 401 Unauthorized\r\n'
header: WWW-Authenticate: Digest realm="IPCamera Login", nonce="d2196ed82d421beea792716429f434d0", qop="auth"
header: Content-Type: text/html
header: Content-Length: 351
header: Connection: close
header: Date: Tue, 07 Mar 2017 21:09:09 GMT
header: Server: lighttpd/1.4.35
"GET /mjpeg/stream.cgi?chn=1 HTTP/1.1" 401 351
send: 'GET /mjpeg/stream.cgi?chn=1 HTTP/1.1\r\nHost: dyndns-host:8091\r\nAuthorization: Digest username="admin", realm="IPCamera Login", nonce="d2196ed82d421beea792716429f434d0", uri="/mjpeg/stream.cgi?chn=1", response="caf37f39406629b9aee0eba02ded2e75", qop="auth", nc=00000001, cnonce="bb118369fb119c46"\r\nAccept-Encoding: gzip, deflate\r\nAccept: /\r\nUser-Agent: python-requests/2.3.0 CPython/2.7.3 Linux/3.2.0-102-generic\r\n\r\n'
reply: 'HTTP/1.1 200 OK\r\n'
header: Cache-Control: public,max-age=0
header: Accept-Ranges: bytes
header: Content-Type: multipart/x-mixed-replace;boundary=ipcamera
header: Connection: close
header: Transfer-Encoding: chunked
header: Date: Tue, 07 Mar 2017 21:09:10 GMT
header: Server: lighttpd/1.4.35
"GET /mjpeg/stream.cgi?chn=1 HTTP/1.1" 200 None
Connected to stream source, boundary separator: --ipcamera
I can see the to-be-relayed stream OK from the internet and on my local network. When I run the mjpeg-relay, I can see the status page and I do see a incoming bandwidth. When I connect to the /stream URL, I do see that the outbound bandwidth goes up. But 1. I do not see the mjpeg in the browser/-Tag. 2. Also VLC does not play the outgoing stream. I tried running the relay on a different server but makes no difference. Anything else I can look at?
The text was updated successfully, but these errors were encountered: