# Stream files always gets connected even if the Stream URI is invalid/wrong **URL:** \ **Category:** Wowza Streaming Engine\ **Tags:** server-administration\ **Created:** [November 19, 2020, 2:02pm UTC](https://community.wowza.com/t/stream-files-always-gets-connected-even-if-the-stream-uri-is-invalid-wrong/92370 "2020-11-19T14:02:46Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Alok\_Kumar2](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@Alok\_Kumar2](https://community.wowza.com/u/Alok_Kumar2)\ **Post date:** [November 19, 2020, 2:02pm UTC](https://community.wowza.com/t/stream-files-always-gets-connected-even-if-the-stream-uri-is-invalid-wrong/92370/1 "2020-11-19T14:02:46Z")
Hi, I am connecting to IP cameras by registering them as a stream files. To register a stream file, we need to populate `"Enter a name"` and `"Stream URI`". fields. Consider a stream file “`Test.stream`” and the corresponding Stream URI is `rtsp://invalidurl` The stream file gets added through the engine manager. Now when I try to connect to this stream through the engine manager, it gest connected and I could see it listed it in the `Incoming Streams` tab. Although after getting connected, the Status of the stream is always _ **Waiting for Stream** _ and it never becomes _ **Active** _ as the RTSP uri is invalid but I expect that this connection itself should fail as the RTSP uri for the stream does not actually exist. is this the default behaviour of the ‘_ **connect to the stream** _’ feature using engine manager, what are the scenarios in which this connection fails if any ? ---
**Author:** ![video\_streaming](https://avatars.discourse-cdn.com/v4/letter/v/22d042/32.png) [@video\_streaming](https://community.wowza.com/u/video_streaming)\ **Post date:** [November 19, 2020, 11:11pm UTC](https://community.wowza.com/t/stream-files-always-gets-connected-even-if-the-stream-uri-is-invalid-wrong/92370/2 "2020-11-19T23:11:33Z")
It could be the IP camera authentication requirement which can vary depending on manufacturer, the encoder settings, the URI is incorrect, a firewall, but it’s usually the URI is incorrect. Waiting for Stream as you figured out is Engine is unable to ingest that stream. Again it’s usually a URI error and it will time out eventually. Do you have the RTSP/ IP camera debugging boolean set to true? **rtspDebugSession:** Boolean _Enables extra debug information in the log file about the RTSP handshake between Wowza Streaming Engine and the IP camera (RTSP/RTP source). Due to the large volume of data that’s logged, this setting shouldn’t be enabled in production environments unless there is a problem that must be investigated. For more details, see [Add RTSP debugging to the log](https://www.wowza.com/docs/how-to-re-stream-video-from-an-ip-camera-rtsp-rtp-re-streaming#add-rtsp-debugging-to-the-log)._ **Default:** false I can share a couple of docs that may help you, but you may need to send us a support ticket for us to test and debug. Sometimes, it can be too difficult to know the problem without a full review of your configuration. [https://www.wowza.com/docs/how-to-create-and-use-stream-files-in-wowza-streaming-engine-manager](https://www.wowza.com/docs/how-to-create-and-use-stream-files-in-wowza-streaming-engine-manager) I’d take a close look at the examples for RSTP stream files here as well: [https://www.wowza.com/docs/how-to-specify-per-stream-settings-in-stream-files#rtspstreams](https://www.wowza.com/docs/how-to-specify-per-stream-settings-in-stream-files#rtspstreams) ---
**Author:** ![Alok\_Kumar2](https://avatars.discourse-cdn.com/v4/letter/a/3ec8ea/32.png) [@Alok\_Kumar2](https://community.wowza.com/u/Alok_Kumar2)\ **Post date:** [November 20, 2020, 4:21pm UTC](https://community.wowza.com/t/stream-files-always-gets-connected-even-if-the-stream-uri-is-invalid-wrong/92370/3 "2020-11-20T16:21:18Z")
Hi, I have set the **rtspDebugSession** property to true in my environment. I understood from your explanation that the stream will time out eventually after some time if the URI is incorrect. However I am asking about the initial connection to a stream file itself which always provides a success message. Can you provide me any example/scenario if which the initial connection itself will fail ?