vukanS

Problem:
The client wants to configure WPML to use different domains for different languages and add a custom NGINX rule so that when users visit specific URLs (like fishingbooker.de/blog), they are redirected to the corresponding language version on the main site (fishingbooker.com/blog).
Solution:
We recommend using an NGINX reverse proxy to route traffic from each language-specific domain to the appropriate language directory on the main WordPress installation. Here is an example of how you can set up the NGINX reverse proxy:

# On fishingbooker.de server<br />location /blog/ {<br />    proxy_pass https://fishingbooker.com/blog/de/;<br />    proxy_set_header Host fishingbooker.com;<br />    proxy_set_header X-Real-IP $remote_addr;<br />    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br />}

# On fishingbooker.ru server<br />location /blog/ {<br />    proxy_pass https://fishingbooker.com/blog/ru/;<br />    proxy_set_header Host fishingbooker.com;<br />    proxy_set_header X-Real-IP $remote_addr;<br />    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;<br />}

Please ensure SSL, cookies, and caching are properly managed, as these are crucial for WordPress and WPML functionality. Note that this solution is not a WPML-native feature and falls outside our standard support. If you need further assistance with server configuration, consider contacting a certified WPML developer from our list of contractors.

This solution might be outdated or not applicable to your specific case. If it doesn't resolve your issue, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please open a new support ticket at our support forum.