GitHub user soulfulgent added a comment to the discussion: Cloudstack 4.22 - 
Configuration Wizard failing - Fix Error

Hi Ryan,


Ahh, ok, I see what you're saying. I seen those entries also, but they were in 
a disabled state, so I figured that wouldn't matter. However, I stand 
corrected. Good to know. I saved those DB queries in my troubleshooting notes.


I will blow a way the DB and re-run the wizard, using 10.10.10.0/24 as my Guest 
Network. Will get back to you later tonight or tomorrow


What would my gateway be, I'm assuming 10.10.10.1? ...obviously I cannot use 
172.16.0.1,  which is my gateway to the internet on my internal network. How 
will my guest VM instances (10.10.10.0/24) communicate with my internal network 
and  servers on 172.16.0.0/16? I have a few servers, like exchange, domain 
controllers ...etc that I need to communicate with on 172.16.0.0/16


Thanks again for  your assistance - Greatly appreciated.


Mike



________________________________
From: RyanP-Testing ***@***.***>
Sent: Tuesday, September 8, 2026 5:35 AM
To: apache/cloudstack
Cc: soulfulgent; Mention
Subject: Re: [apache/cloudstack] Cloudstack 4.22 - Configuration Wizard failing 
- Fix Error (Discussion #13956)


Hi Mike,

Based on your DB query results, the issue is clear.

You have 6 physical network records (IDs 200-205) from repeated wizard 
attempts. The wizard is confused because:

Your guest traffic is on "Physical Network 2" (ID 205)

But the isServiceProviderEnabled check may be resolving against an older 
"Physical Network 1" (ID 204 or earlier)

Several old networks are in Disabled state but still present

Recommended Fix:

Since this is a test installation with no production data, do a clean database 
recreate:

bash
sudo cloudstack-setup-databases cloud:password@<DB_IP> --deploy-as=root: 
--force-recreate
Then run the wizard once without interruption.

Important for Guest CIDR:

Do not use 172.16.0.0/16 for guest. It overlaps with your infrastructure 
network. Use a completely separate range like:

10.10.10.0/24

192.168.100.0/24

Why this matters:
Overlapping guest and infrastructure CIDRs breaks routing and Virtual Router 
deployment.

After fresh install:

Run wizard once — don't retry if it fails

Use separate guest CIDR

Check management-server.log if any errors

Verify only ONE physical network exists after wizard

This will resolve the wizard error and the VM console/ISO issues.

Regards,
Ryan P.
Cloud & DevOps Engineer
AccuWeb.Cloud

—
Reply to this email directly, view it on 
GitHub<https://github.com/apache/cloudstack/discussions/13956?email_source=notifications&email_token=B2X6LXUN4ODRJUOT3L6KCI35N7HGBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGQ3DIMRQUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18346420>,
 or 
unsubscribe<https://github.com/notifications/unsubscribe-auth/B2X6LXU5VHI3OPHDTOOXYDL5N7HGBAVCNFSNUABGKJSXA33TNF2G64TZHM4TONJZGQ2DQO2ENFZWG5LTONUW63R3GEYDMNRYGE3DLILWAI>.
Triage notifications, keep track of coding agent tasks and review pull requests 
on the go with GitHub Mobile for 
iOS<https://github.com/notifications/mobile/ios/B2X6LXWEI6SITAOHB22EEYT5N7HGBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGQ3DIMRQUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
 and 
Android<https://github.com/notifications/mobile/android/B2X6LXUGJB2JXBX3NUGT2ML5N7HGBA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBTGQ3DIMRQUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
 Download it today!
You are receiving this because you were mentioned.Message ID: ***@***.***>


GitHub link: 
https://github.com/apache/cloudstack/discussions/13956#discussioncomment-18359041

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to