Change in Web and App server IPs | Community
Skip to main content
A
ash20
Level 2
October 16, 2023
Solved

Change in Web and App server IPs

  • October 16, 2023
  • 2 replies
  • 3723 views

If the IP's of web and app server changes, where to do have to update it in the adobe campaign classic v7(onprem mid deployment) configuration so that it keeps connected ?


i can see the web IPs in the deployment wizard in "Access from the Internet" tab under "Internal URLs of the frontal servers" section i believe this needs to be updated.

 

what are the other places this needs to be updated?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by jorgeferreira

Hi, 

 

Ideally this should be managed by the infra/network team.

 

However, here are some links that can be helpful:

 

Essencially, what you need to make sure is that <yournameserver> points to the correct IP.

For example:

 

You have 1 server named acprod on 172.1.1.2. 

If you change the ip server to 172.1.1.3, the DNS record that knows who is acprod, needs to be updated so that all the network still knows who is acprod. 

2 replies

Marcel_Szimonisz
Community Advisor
Marcel_SzimoniszCommunity Advisor
Community Advisor
October 16, 2023

Hello @ash20 ,

normally, localhost:8080, is put there instead of IP, is that somehting you can do and try? 

Marcel Szimonisz

A
ash20Author
Level 2
October 17, 2023

Dear @marcel_szimonisz ,

 

I changed it to "LocalHost:8080" and tried to publish a web application and got the below error,

 

"RED-520028 The URL 'localhost:8080' of remote redirection server is not a valid URL."
 
I think here it should be the frontal server IPs.
 
 
jorgeferreira
jorgeferreira
Level 3
October 17, 2023

Dear @jorgeferreira ,

 

i restored to the original setting from LocalHost:8080 

 

but now i see a different error 

 

"RED-520025 Communication failed with tracking server 'https://webappservers.local.network'. Please check that the server is started and check if the connection parameters defined in the deployment wizard (or directly in the options), are correct."

 

 

i saw same issue was resolved by resolved by restarting mid in other case, but i tried still getting same error 

 


can you ping the server by that URL? Also, if the port is different from 80 or 433, you must put it there

jorgeferreira
jorgeferreira
Level 3
October 16, 2023

Hi, 

 

As long as you keep DNS records up to date, you shouldn't have any issues. This means that the DNS server your company has, needs to update the IP of the servers as soon as possible (some downtime can happen).

 

 

A
ash20Author
Level 2
October 17, 2023

Dear @jorgeferreira ,

 

how can i get the records that needs to be update on the DNS ?

jorgeferreira
jorgeferreiraAccepted solution
Level 3
October 17, 2023

Hi, 

 

Ideally this should be managed by the infra/network team.

 

However, here are some links that can be helpful:

 

Essencially, what you need to make sure is that <yournameserver> points to the correct IP.

For example:

 

You have 1 server named acprod on 172.1.1.2. 

If you change the ip server to 172.1.1.3, the DNS record that knows who is acprod, needs to be updated so that all the network still knows who is acprod. 

    Terms & ConditionsAccessibility statement

    Loading footer...