Skip to main content
maxpixelview
maxpixelview
Participant
May 8, 2026

SRT streaming not using passphrase auth in 26.2.2

  • May 8, 2026
  • 1 reply
  • 21 views

When attempting to stream with SRT protocol as a caller it seems like Premiere is not correctly using the passphrase that I enter and instead its starting the stream unsecured. 

On my server I get these errors from the SRT protocol. 

!-->

:10:15.122626/SRT:RcvQ:w2!W:SRT.cn: processConnectRequest: rsp(REJECT): 1011 - Password required or unexpected

14:10:15.214513/SRT:RcvQ:w2*E:SRT.cn: @566080749: HS EXT: Agent declares encryption, but Peer does not - rejecting connection per enforced encryption.

14:10:15.214592/SRT:RcvQ:w2!W:SRT.cn: @566080749:newConnection: connection rejected due to: INTERNAL REJECTION - ERROR:UNSECURE

 

The exact same settings work fine when using Premiere 25.0. Streaming also works if I turn off the passphrase requirement in the server and send it unencrypted from Premiere. 

 

So seems like passphrase is not added properly in Premiere 26.2.2. 

    1 reply

    IanB_360
    Community Manager
    IanB_360Community Manager
    Community Manager
    May 25, 2026

    Hi ​@maxpixelview 

    A few questions that may help narrow this down:

    • What operating system are you using?
    • Can you confirm whether the issue occurs with multiple SRT servers, or only this specific server implementation?
    • Are you using Caller mode exclusively, or have you tested Listener/Caller combinations?
    • Does the issue occur with a newly created streaming preset in 26.2.2?
    • Are there any special characters in the passphrase being used?

    The server logs are particularly useful since they appear to indicate that the server is expecting an encrypted connection while the client is attempting to connect without encryption:

    • "Password required or unexpected"
    • "Agent declares encryption, but Peer does not"
    • "UNSECURE"

    If possible, could you also provide:

    • The exact Premiere Pro 25.0 build and 26.2.2 build numbers.
    • The SRT server software/version being used.
    • A screenshot of the SRT output settings (with any sensitive information redacted).

    Thanks for including the protocol logs—they help clarify what the server is seeing during the connection attempt.

    Here to help

    Ian

    maxpixelview
    maxpixelviewAuthor
    Participant
    May 25, 2026

       Hi Ian,

       Additional details:

       - Client OS: macOS 15.7.7 (we also tested Tahoe)
       - Premiere Pro version: 26.2.2 build 3
       - Server OS: Debian 12
       - Server setup: remote virtual machine with a public IP and DNS name
       - Premiere is being used as SRT caller. We only tested caller mode because that is the workflow used to dial into our SRT server.
       - This was not a saved preset. The SRT details were entered manually in Premiere.
       - Passphrase used for testing: 1234567890
       - No special characters in the passphrase.

     

       To eliminate our own server implementation as the cause, we reproduced this with a minimal stock FFmpeg Docker image using the SRT protocol.

       Image:

       jrottenberg/ffmpeg:8.1-ubuntu2404

       FFmpeg reports --enable-libsrt and lists srt under supported protocols.

     

       Server command:

    docker run --rm -it \
         -p 20000:20000/udp \
         jrottenberg/ffmpeg:8.1-ubuntu2404 \
         -i 'srt://:20000?mode=listener&passphrase=1234567890&pbkeylen=16' \
         -f null -

     

       When streaming from Premiere Pro 26.2.2 build 3 to this listener, with the passphrase set to 1234567890, the connection fails with the same SRT encryption/auth errors as before. The server appears to expect encryption, but Premiere appears to connect without applying the passphrase.

     

       As another check, if we run the same FFmpeg listener without a passphrase requirement, Premiere 26.2.2 streams successfully. It works both when the passphrase field in
     Premiere is empty and when the passphrase field contains 1234567890. This seems to confirm that Premiere is not actually applying/sending the passphrase in 26.2.2.
     

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices