Set-ExecutionPolicy Bypass
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
ip.addr == 104.19.230.21
ip.addr matches packets where the source OR destination IP is 104.19.230.21.
It works for both IPv4 and IPv6 (though here it’s IPv4).
You could also use:
ip.src == 104.19.230.21 or ip.dst == 104.19.230.21
If you want to see only traffic from that IP (responses to you), use ip.src == 104.19.230.21.
If you want only traffic to that IP (your requests), use ip.dst == 104.19.230.21.
Add the following code to your wp-config.php file, right before the line that says /* That's all, stop editing! Happy publishing. */
$domain = array("domain1.com", "www.domain1.com", "domain2.com", "www.domain2.com");
if (in_array($_SERVER['HTTP_HOST'], $domain)) {
define('WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST']);
define('WP_HOME', 'http://' . $_SERVER['HTTP_HOST']);
}
This code dynamically sets the site URL based on how a visitor accesses the site, ensuring both domains work correctly.
Important Considerations:
Allow All Domains: If you want to allow any domain pointing to your server, replace the if (in_array(...)) block with just the two define lines, though using the domain array is safer to prevent unwanted access.
HTTPS Support: If your site uses HTTPS, change 'http://' to 'https://' in both define statements.
Subdirectory Installations: If WordPress is in a subdirectory (e.g., /wp), modify the code accordingly: define('WP_SITEURL', 'http://' . $_SERVER['HTTP_HOST'] . '/wp');.
Avoid Plugin Conflicts: When testing, temporarily deactivate plugins to check for conflicts.