Sync Issues in Nextcloud: Troubleshooting Asymmetric Routing and Split DNS Setup
Budget: $30 – $250 USD
We are looking for a freelancer with strong expertise in firewalls and networking.
Current Issue:
We have a network setup that includes a DMZ, an internal LAN, and a management network (MGMT). Our Nextcloud server is located behind the DMZ. While connections to Nextcloud from external sources work perfectly fine, we are encountering issues when connecting from the internal LAN to the DMZ (Nextcloud server).
The Nextcloud client frequently throws the following error message:
"Expected file size of 135,142 bytes but got 49,152 bytes read (from the Nextcloud client) and written (to Nextcloud storage). This might be caused by a network issue on the sending side or a storage writing issue on the server side."
We are utilizing DNS split-horizon and suspect that the problem stems from asymmetric routing somewhere within the setup.
Current Issue:
We have a network setup that includes a DMZ, an internal LAN, and a management network (MGMT). Our Nextcloud server is located behind the DMZ. While connections to Nextcloud from external sources work perfectly fine, we are encountering issues when connecting from the internal LAN to the DMZ (Nextcloud server).
The Nextcloud client frequently throws the following error message:
"Expected file size of 135,142 bytes but got 49,152 bytes read (from the Nextcloud client) and written (to Nextcloud storage). This might be caused by a network issue on the sending side or a storage writing issue on the server side."
We are utilizing DNS split-horizon and suspect that the problem stems from asymmetric routing somewhere within the setup.