GitHub user nickaccuweb added a comment to the discussion: Cloudstack 4.22 - Configuration Wizard failing - Fix Error
@soulfulgent Thanks for the screenshot. I can see why this is getting confusing, especially since the wizard and manual Guest network creation screens ask for different information. The good news is that this particular error is straightforward. In your screenshot, you've configured: - Gateway: 100.100.100.1 - Netmask: 255.255.255.0 - Guest IP range: 100.100.100.2 to 100.100.100.100 However, you've entered an external IP address in the **"IPv4 address for the VR in this Network"** field. CloudStack is rejecting the request because the specified Virtual Router IP isn't within the Guest network's IP range. For your next attempt, I suggest leaving that Virtual Router IPv4 field blank. According to the CloudStack documentation, it's optional, and CloudStack can automatically allocate an address where applicable. If you need to specify it manually, it must be an available address within the Guest IP range, not your external public IP. Regarding your other questions: **Yes, your Guest network should use a different, non-overlapping subnet from your Management network.** Your previous choice of 10.10.10.0/24 was reasonable, provided it matches the network you've configured on the Guest-side interface. The standalone Guest network form exposes more configuration options than the initial wizard. That explains why you're seeing additional fields. Also, we shouldn't need a new Guest network just to complete the original setup. I suggested creating one manually mainly to check whether CloudStack accepts an untagged shared network outside the wizard. Here's what I'd like you to check next: 1. Try creating the shared Guest network with the Virtual Router IPv4 field blank. 2. Use an unused, non-overlapping Guest subnet that is actually configured and reachable on your Guest network. 3. Select Physical Network 2 (cloudbr1) and the security-group-enabled shared network offering. 4. For VLAN/VNI, test the untagged option, without entering VLAN 800. 5. Verify that the SecurityGroupProvider is enabled on Physical Network 2. One important point: since defaultGuestNetwork already exists with VLAN 800 and 10.10.10.0/24, we should avoid creating another overlapping Guest network or changing the existing one until we know the new configuration is valid. If the manual untagged network creation succeeds, we'll know the standalone network creation process works and can focus on the original wizard behavior. If it fails again, please share the new API error. That will give us a clearer indication of whether the issue is with the untagged network configuration or the wizard itself. I wouldn't recommend switching CloudStack versions or recreating the database at this stage. Reference: https://docs.cloudstack.apache.org/en/4.22.0.0/adminguide/networking/advanced_zone_config.html Thanks for sticking with the troubleshooting. Regards, Nick R AccuWeb.Cloud GitHub link: https://github.com/apache/cloudstack/discussions/13956#discussioncomment-19603181 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
