Expand my Community achievements bar.

Announcing the launch of new sub-community for Campaign Web UI to cater specifically to the needs of Campaign Web UI users!
SOLVED

Unable to Login to Adobe Client Console

Avatar

Level 3

Hi Team,

 

We had recently observed an issue while trying to login to one of our production environments. PFB screenshot for the same.

AnushkaRajan_0-1587116240481.png

 

The error got resolved post appending port number to the URL. However, I have been using the environment since a long time without the port number in the instance url.

 

Could anybody please help me understand what might have caused this change and why has the port number become a mandatory parameter in my instance URL now ?

 

I would also like to mention that this issue was observed only on one of my production instance. I am able to access the other instance without appending the port number in the instance URL.

 

Regards,

Anushka

1 Accepted Solution

Avatar

Correct answer by
Level 5

Hi,

 

Default port when making html call is 80, if that is changed you have to provide the port number on the instance url.

Let's say you are using windows IIS for redirection, default site in IIS will have 80. If you are using the default site for campaign redirection, you can access instance without port, else you have to provide the port that is used on that site.

Check if your redirection config might have recently changed by some one.

 

-Prasanna.

View solution in original post

4 Replies

Avatar

Correct answer by
Level 5

Hi,

 

Default port when making html call is 80, if that is changed you have to provide the port number on the instance url.

Let's say you are using windows IIS for redirection, default site in IIS will have 80. If you are using the default site for campaign redirection, you can access instance without port, else you have to provide the port that is used on that site.

Check if your redirection config might have recently changed by some one.

 

-Prasanna.

Avatar

Level 3
Hi Prasanna, Thanks for the update. I checked the IIS for redirection config which is set to the default 80 port. I retried logging in to my client console without the port number 8080 in my connection URL and now it works. Is there any other possible reason that could have caused this change. Regards, Anushka