Error en la base de datos de WordPress: [Disk full (/opt/bitnami/mariadb/tmp/#sql-temptable-1e9013-6a6700-132fef.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_options`

Error en la base de datos de WordPress: [Disk full (/opt/bitnami/mariadb/tmp/#sql-temptable-1e9013-6a6700-132ff3.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SELECT wp_posts.* FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND wp_posts.post_name IN ('front-page') AND ( wp_term_relationships.term_taxonomy_id IN (350,368) ) AND ((wp_posts.post_type = 'wp_template' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'acf-disabled'))) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC

Error en la base de datos de WordPress: [Disk full (/opt/bitnami/mariadb/tmp/#sql-temptable-1e9013-6a6700-132ff6.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SELECT wp_posts.* FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND wp_posts.post_name IN ('page','page-14','page-inicio') AND ( wp_term_relationships.term_taxonomy_id IN (350,368) ) AND ((wp_posts.post_type = 'wp_template' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'acf-disabled'))) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC

Error en la base de datos de WordPress: [Disk full (/opt/bitnami/mariadb/tmp/#sql-temptable-1e9013-6a6700-132ff9.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SELECT wp_posts.* FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND wp_posts.post_name IN ('checkout') AND ( wp_term_relationships.term_taxonomy_id IN (350,368) ) AND ((wp_posts.post_type = 'wp_template' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'acf-disabled'))) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC

Error en la base de datos de WordPress: [Disk full (/opt/bitnami/mariadb/tmp/#sql-temptable-1e9013-6a6700-132ffa.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SELECT wp_posts.* FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND wp_posts.post_name IN ('mini-cart') AND ( wp_term_relationships.term_taxonomy_id IN (350,368) ) AND ((wp_posts.post_type = 'wp_template_part' AND (wp_posts.post_status = 'publish' OR wp_posts.post_status = 'acf-disabled'))) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC

Error en la base de datos de WordPress: [Disk full (/opt/bitnami/mariadb/tmp/#sql-temptable-1e9013-6a6700-132ffc.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")]
SELECT wp_posts.* FROM wp_posts LEFT JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND ( wp_term_relationships.term_taxonomy_id IN (472) ) AND wp_posts.post_type = 'product' AND ((wp_posts.post_status = 'publish')) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC

Remove Web Application Proxy Server From Cluster [verified] May 2026

Siguenos

Remove Web Application Proxy Server From Cluster [verified] May 2026

To remove a Web Application Proxy (WAP) server from a cluster, you can use either PowerShell to clean up the configuration or the Server Manager wizard to decommission the server role entirely.

Option 1: Using PowerShell (Quickest for Configuration Cleanup)

If the server has already been decommissioned or if you just want to remove its entry from the management console's cluster list, use the following commands on a remaining healthy WAP server:

List existing servers:Identify the exact name of the server you wish to remove. powershell (Get-WebApplicationProxyConfiguration).ConnectedServersName Use code with caution. Copied to clipboard

Update the cluster list:Run this command to keep only the servers you want. Replace the names in the list with your actual healthy servers. powershell

Set-WebApplicationProxyConfiguration -ConnectedServersName "HealthyServer1.domain.com", "HealthyServer2.domain.com" Use code with caution. Copied to clipboard

Note: In some scenarios, you can also filter out the unwanted server dynamically: powershell

Set-WebApplicationProxyConfiguration -ConnectedServersName ((Get-WebApplicationProxyConfiguration).ConnectedServersName -ne 'ServerToRemove.domain.local') Use code with caution. Copied to clipboard Option 2: Using Server Manager (Full Role Uninstallation)

To properly decommission a server and remove the WAP role from the machine itself, follow these steps:

Remove Published Applications: Open the Remote Access Management Console and delete any web applications published specifically through this node. Uninstall the Role:

Open Server Manager and select Manage > Remove Roles and Features. Follow the wizard to the Server Roles page.

Uncheck Remote Access (or specifically the Web Application Proxy sub-role). Restart the server when prompted to complete the removal.

Clean up AD FS Trust (Optional): If you are retiring the server permanently, you can also remove its proxy trust certificate from the local store. Important Considerations

Permissions: You must have Local Administrator permissions on the WAP server and sufficient privileges on the AD FS server to modify the configuration.

Version Compatibility: Configuration changes must generally be made from a WAP server running the oldest version if you are in a mixed-version cluster environment.

External Access: Removing a node might impact external access if your Network Load Balancer (NLB) is not updated to stop sending traffic to the removed IP.

Removing a Web Application Proxy Server from a Cluster: A Comprehensive Review remove web application proxy server from cluster

Introduction

A Web Application Proxy (WAP) server is a crucial component of a cluster infrastructure, providing secure and reliable access to web applications. However, there may be situations where a WAP server needs to be removed from a cluster, such as planned maintenance, upgrades, or replacement with a new server. In this review, we will discuss the process of removing a WAP server from a cluster, its implications, and best practices to ensure a smooth transition.

Understanding Web Application Proxy Server Clusters

Before diving into the removal process, it's essential to understand the basics of WAP server clustering. A cluster is a group of servers that work together to provide a single, unified service, such as web application proxying. Clustering provides high availability, scalability, and fault tolerance, ensuring that if one server fails, the other servers can take over its responsibilities.

Reasons for Removing a WAP Server from a Cluster

There are several reasons why a WAP server might need to be removed from a cluster:

  1. Hardware upgrades or replacement: The server hardware may be outdated, and it's time to upgrade or replace it with newer, more efficient equipment.
  2. Software updates or patches: The server may require significant software updates or patches that cannot be applied while it's still part of the cluster.
  3. Maintenance or decommissioning: The server may need to be taken offline for maintenance, or it may be decommissioned due to changes in business requirements.
  4. Capacity adjustments: The cluster may need to be adjusted to accommodate changes in traffic or workload, requiring the removal of underutilized servers.

Preparation Steps

Before removing a WAP server from a cluster, it's essential to:

  1. Verify cluster configuration: Review the cluster configuration to ensure that the WAP server is not critical to the cluster's operation.
  2. Check server dependencies: Identify any dependencies on the WAP server, such as downstream servers or applications that rely on it.
  3. Notify stakeholders: Inform stakeholders, including administrators, developers, and end-users, about the planned removal and potential impact on services.
  4. Backup configuration and data: Backup the WAP server's configuration and data to prevent loss during the removal process.

Removing the WAP Server from the Cluster

The steps to remove a WAP server from a cluster vary depending on the specific clustering technology and configuration. However, the general process involves:

  1. Drain the server: Gradually move all connections and traffic away from the WAP server to be removed.
  2. Remove server from cluster: Use the clustering software or management tools to remove the WAP server from the cluster.
  3. Update cluster configuration: Update the cluster configuration to reflect the changes and ensure that the remaining servers can continue to provide services.

Post-Removal Tasks

After removing the WAP server from the cluster:

  1. Verify cluster health: Check the cluster's health and ensure that all servers are functioning correctly.
  2. Test services: Test services and applications to ensure they are still accessible and functioning as expected.
  3. Decommission or repurpose the server: Decommission the removed server or repurpose it for other uses.

Best Practices

To ensure a smooth transition when removing a WAP server from a cluster:

  1. Plan ahead: Schedule the removal during a maintenance window to minimize impact on services.
  2. Communicate with stakeholders: Keep stakeholders informed throughout the process.
  3. Test thoroughly: Verify that services and applications are functioning correctly after the removal.
  4. Document changes: Update documentation to reflect changes to the cluster configuration.

Conclusion

Removing a WAP server from a cluster requires careful planning, preparation, and execution to ensure minimal disruption to services. By following best practices and understanding the implications of removal, administrators can ensure a smooth transition and maintain the high availability and scalability of their web application proxy services. To remove a Web Application Proxy (WAP) server

To remove a Web Application Proxy (WAP) server from a cluster (or "farm"), you must update the cluster configuration to exclude the decommissioned server and then uninstall the Remote Access role from the server itself. 1. Update the Cluster Configuration

When a server is decommissioned or fails, it often still appears in the WAP cluster list. You must manually update the ConnectedServersName property to remove the stale entry. View current servers : Open PowerShell as an Administrator and run: powershell

(Get-WebApplicationProxyConfiguration).ConnectedServersName ``` Use code with caution. Copied to clipboard Remove the specific server : Execute the following command, replacing 'ServerToRemove.domain.local' with the FQDN of the server you want to remove: powershell

Set-WebApplicationProxyConfiguration –ConnectedServersName ((Get-WebApplicationProxyConfiguration).ConnectedServersName –ne 'ServerToRemove.domain.local') ``` *Note: `Swpc` and `gwpc` are common aliases

`Set-WebApplicationProxyConfiguration` and `Get-WebApplicationProxyConfiguration` respectively.* Use code with caution. Copied to clipboard 2. Decommission the Server Role

Once the server is no longer recognized as part of the cluster, you should uninstall the WAP services from the physical or virtual machine. Via PowerShell powershell

Uninstall-WindowsFeature Web-Application-Proxy, CMAK, RSAT-RemoteAccess ``` Use code with caution. Copied to clipboard Via Server Manager (GUI) Server Manager and select Remove Roles and Features Select the server and uncheck the Remote Access Confirm the removal of features and click 3. Post-Removal Cleanup Load Balancers

: Remove the decommissioned server's IP address from any external or internal Load Balancer pools DNS Records : Delete any DNS A or AAAA records that point to the removed server. Certificates : If the server is being permanently decommissioned, delete the SSL certificates from its local store to ensure security. Microsoft Learn Are you removing a server to replace it with a newer version , or are you shrinking the cluster permanently?

Decommissioning a Web Application Proxy - Packt Subscription

How to Remove a Web Application Proxy (WAP) Server from a Cluster Removing a Web Application Proxy (WAP)

server from a cluster involves both logical removal from the configuration and physical uninstallation of the server role. Whether you are decommissioning an old server or troubleshooting a duplicate entry, following a clean removal process ensures your Active Directory Federation Services (AD FS) farm remains healthy. 1. Identify the Server to Remove

Before taking action, verify the current list of connected servers in your WAP cluster. PowerShell Command : Run the following on an active WAP node: powershell (Get-WebApplicationProxyConfiguration).ConnectedServersName Use code with caution. Copied to clipboard

This returns the fully qualified domain names (FQDNs) of all servers currently recognized as part of the WAP cluster. 2. Logical Removal from the Cluster

If a server has been powered off or failed without being uninstalled, it may still appear in the cluster list. You must manually update the ConnectedServersName property to exclude it. Open PowerShell as an Administrator. Set a new list that includes every server the one you want to remove: powershell

Set-WebApplicationProxyConfiguration -ConnectedServersName ((Get-WebApplicationProxyConfiguration).ConnectedServersName -ne 'server-to-remove.domain.local') Use code with caution. Copied to clipboard 'server-to-remove.domain.local' with the actual FQDN of the target server. 3. Uninstall the WAP Role (If Accessible)

If the server is still running and accessible, follow these steps to cleanly uninstall the role: Remove Published Applications : Open the Remote Access Management Console and remove any web applications assigned to this server. Uninstall Features Hardware upgrades or replacement : The server hardware

: Run the following PowerShell command to remove the WAP role and related features: powershell

Uninstall-WindowsFeature Web-Application-Proxy, CMAK, RSAT-RemoteAccess Use code with caution. Copied to clipboard Alternatively, use the Remove Roles and Features Wizard Server Manager : A restart is required to complete the removal. 4. Final Cleanup

To ensure no "ghost" settings remain, perform these final checks: DNS Entries

: Delete any DNS A-records or CNAMEs specifically pointing to the removed server. Load Balancer

: If using an external load balancer, remove the server's IP address from the backend pool. Certificates

: If the server is being decommissioned permanently, revoke or delete any local ADFS ProxyTrust certificates. WAP – How to remove a WAP Server from WAP clusters

4. Pre-Removal Preparation

Best Practices Checklist for WAP Cluster Maintenance

✅ Always maintain an odd number of WAP nodes (1, 3, 5) when using default load balancer session persistence. Even-numbered clusters can cause split-brain conditions during AD FS proxy trust certificate renewal.

✅ Document the removal in your CMDB – including dates, who performed the removal, and the reason.

✅ Update your disaster recovery plan – change the recovery order to exclude the removed server.

✅ Monitor remaining node capacity. If total CPU on remaining nodes exceeds 70% sustained, add a replacement node before removing a second one.

✅ Schedule certificate rollover after removal. The AD FS proxy trust certificate (default 1-year) does not need immediate reissue, but after a cluster size change, run:

Update-AdfsCertificate -CertificateType Proxy-Trust

Remove by ID (assuming the server name is unavailable for standard targeting)

Remove-AdfsWebApplicationProxy -TargetWebApplicationProxy <ProxyObject>

Using Server Manager

  1. Open Server Manager on the target WAP server.
  2. Go to Manage > Remove Roles and Features.
  3. Proceed to the Server Roles section.
  4. Uncheck Remote Access > Web Application Proxy.
  5. Complete the wizard and restart if prompted.

Step 5: Verify Successful Removal

Perform the following checks:

  1. No pending authentication requests – Monitor the AD FS event log for any lingering proxy errors.

  2. Cluster health – On a remaining WAP server, run:

    Get-WebApplicationProxyConfiguration

    The removed server should not appear.

  3. External access – Use a client outside your network to log into a federated application. Authentication should work via the remaining WAP servers.

Watch for errors

Get-EventLog -LogName "Web Application Proxy" -Newest 10