Does not want to Prerolled Error?

cmd pipeline = gst-launch-1.0 -v rtspsrc location=“rtsp://user:pass@xxx.xxx.xxx.xxx/cam/realmonitor?channel=1&subtype=0” ! rtph265depay ! h265parse ! decodebin ! videoconvert ! autovideosink

Logs

Setting pipeline to PAUSED …
Pipeline is live and does not need PREROLL …
Progress: (open) Opening Stream
Pipeline is PREROLLED …
Prerolled, waiting for progress to finish…
Progress: (connect) Connecting to rtsp://user:pass@xxx.xxx.xxx.xxxcam/realmonitor?channel=1&subtype=0
Progress: (open) Retrieving server options
ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not read from resource.
Additional debug info:
…/gst/rtsp/gstrtspsrc.c(6523): gst_rtsp_src_receive_response (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
Could not receive message. (Timeout while waiting for server response)
ERROR: pipeline doesn’t want to preroll.
ERROR: from element /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0: Could not read from resource.
Additional debug info:
…/gst/rtsp/gstrtspsrc.c(6621): gst_rtspsrc_try_send (): /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0:
Could not receive message. (Timeout while waiting for server response)
ERROR: pipeline doesn’t want to preroll.

The errors seem to indicate that it failed to connect to RTSP server.
Confirm the stream is available and can be understood and played with:

gst-discover-1.0 -v rtsp://user:pass@xxx.xxx.xxx.xxx/cam/realmonitor?channel=1&subtype=0

gst-play-1.0 -v rtsp://user:pass@xxx.xxx.xxx.xxx/cam/realmonitor?channel=1&subtype=0

Thanks for the reply

I have tried with what you suggest but With gst-discoverer-1.0 i am response Analyzing URI timed out and gst-play-1.0 does not providing any output

but the same stream works fine with vlc media player

Not sure, but if your username or password contains some special characters, you may enclose the uri into double quotes:

gst-discover-1.0 -v "rtsp://user:pass@xxx.xxx.xxx.xxx/cam/realmonitor?channel=1&subtype=0"

gst-play-1.0 -v "rtsp://user:pass@xxx.xxx.xxx.xxx/cam/realmonitor?channel=1&subtype=0"

If you’re running an old gstreamer version, I don’t remember what was the actual issue, but something in plugins-ugly was leading to authentication failure. Uninstalling plugins-ugly was a workaround for such case.