Troubleshooting
Diese Seite ist noch nicht in deiner Sprache verfügbar. Englische Seite aufrufen
Support
Section titled “Support”If you have questions that are not answered here or in other documentation, create a service request in the STACKIT Help Center.
Common LB issues
Section titled “Common LB issues”The following issues apply to both STACKIT Network Load Balancer and Application Load Balancer:
Security group assignment to target virtual machines
Section titled “Security group assignment to target virtual machines”Works as intended: All required security groups for STACKIT Load Balancers, including traffic configurations to target virtual machines, are created and assigned automatically during setup. No manual steps are needed.
For example: When you create a load balancer named “demo-lb-01”, a security group named loadbalancer/demo-lb-01/backend is created and added to the servers in the target pool. Ingress ports open according to the ports configured in the target pool.
Internal IP addresses may change after OpenStack resource loss
Section titled “Internal IP addresses may change after OpenStack resource loss”Internal IP addresses are dynamically assigned using OpenStack DHCP. During normal operation, the same internal IP address is reassigned. However, if OpenStack resources are lost, the internal IP address may change.
Loss of all connections during failover
Section titled “Loss of all connections during failover”Because of the active/passive configuration, a connection reset will occur during failover, which may take up to a few seconds. Additionally, sessions will not be transferred to the new VM and clients will need to reconnect.
ALB-specific issues
Section titled “ALB-specific issues”This section lists current known issues for STACKIT Application Load Balancer.
Creation currently only available through API
Section titled “Creation currently only available through API”You can create Application Load Balancers only via the API. A portal interface is in development.