내 커뮤니티 업적 표시줄을 확대합니다.

Submissions are now open for the 2026 Adobe Experience Maker Awards

Mark Solution

활동이 없어 이 대화는 잠겼습니다. 새 게시물을 작성해 주세요.

해결됨

Web applications: Can't preview page on production

Avatar

Level 5

Hello!

We are struggling a bit with Web Applications in Campaign Classic V7 and were hoping that some of you may have pointers to how we can get around the challenge 🙂 

 

We are trying to create an overview page enabling a call center to view a segment of recipients based on a simple query. For that reason we have enabled "access control" on the page. HOWEVER! Whenever we preview the page we see the following error: 

 

"XSV-350048 You need to use a secure URL (https) to access this service

 

BUT, the URL is clearly "https", so we are simply not sure why this is happening.

Additionally, this feature works perfectly fine in staging, but not in production. 

See image for reference.

 

Thanks in advance 

 

SorenDahk_0-1651571852522.png

 

 

1 채택된 해결책 개

Avatar

정확한 답변 작성자:
Level 5

@Sukrity_Wadhwa @Parvesh_Parmar I got the issue resolved through Adobe support. For some reason the redirect was routed to an insecure protocol. They corrected that redirect so now it is working as intended. Thanks for your answer!

원본 게시물의 솔루션 보기

3 답변 개

Avatar

Community Advisor

Hello @SorenDP,

 

Are you hosting this web application on a separate frontal server or the same application server?  For e.g. if you are hosting on the application server, then there you also need to add  an SSL certificate for the domain of the application server. 

 

If you are hosting this frontal server, then add SLS certificate there for the domain which you are using for frontal server. 


Try to access the server with HTTPS URL like open campaign on browser a thin client.

 

 

Thanks. 

Parvesh.  

Parvesh Parmar – Adobe Community Advisor
https://www.linkedin.com/in/parvesh-parmar/

Avatar

정확한 답변 작성자:
Level 5

@Sukrity_Wadhwa @Parvesh_Parmar I got the issue resolved through Adobe support. For some reason the redirect was routed to an insecure protocol. They corrected that redirect so now it is working as intended. Thanks for your answer!

Avatar

Administrator

Hi @SorenDP,

Was the given solution helpful to resolve your query or do you still need more help here? Do let us know.

Thanks!



Sukrity Wadhwa