Issue with using surf:// item in a Lockdown page (Soti Surf)

Hello, I'm having an issue from few days with surf:// items in a Lockdown profiles (it always worked before)

The web page won't open because I can see a typing error in the webpage address, I'm sharing two images, any idea?

ResultConfiguration

a year ago
SOTI MobiControl
ANSWERS
R
Remy
a year ago
A
ABMOD@SOTI
a year ago

 

Hi Daniele,

Thank you for posting on SOTI Pulse, and thank you, Remy, for your response your expertise and willingness to help are greatly appreciated!

Please let us know if the suggested discussion forum addresses your concern. If not, or if you have any additional questions, please don’t hesitate to reach out. We're here to provide support.

Warm regards,

MD
Matt Dermody
a year ago

This has been resolved now in Surf 2025.0.1.

A
ABMOD@SOTI
a year ago

Hi Daniele Aquaro,

Thanks for posting on SOTI Pulse, Thanks Matt , for responding to the post, your expertise and willingness to help are greatly appreciated!

Have you had an opportunity to test the suggested version by Matt, and has it successfully addressed your query?

If not, or If you have any additional questions or concerns, please don't hesitate to reach out. We're dedicated to providing assistance and support.

DA
Daniele Aquaro
a year ago

Hello,

yes, I can confirmed it's solved with new version 2025.0.1

Thanks

A
ABMOD@SOTI
a year ago

Hi Daniele Aquaro,

Thanks for your confirmation.

Also, if this post has helped you in solving your query, I would request you to mark the particular comment as "is solution", so that others may benefit from this information.

Warn Regards,

JS

Hello,
it looks like the issue is related to how the Lockdown surf action handles the URL.

The address seems to be modified before opening.
Example:
the configured address contains HTTPS, but the opened address starts with HTTP and becomes invalid.

Because of that, the page fails with name not resolved.

Direct opening in Chrome should be tested to confirm that the website itself is working.
If Chrome works, then the issue is likely in the Lockdown profile or in the surf URL parsing.

Possible test:
enter the destination without protocol prefix and check if Lockdown still modifies it.

It seems that the URL handling behavior may have changed recently.

Similar Discussions