Can ping and RDP VPN's servers but cannot http/sftp

I am successfully connected to a VPN network, I can RDP to remote PC and ping the servers (remote PC and servers in VPN's network). However, I cannot http/sftp the server's sites through home's modem/router (the site takes a lot of time to load and then return Network Error or Timeout error). When I connect to VPN with mobile hotspot, I can http/sftp to the site without any problem.

I checked the home's network subnet and the VPN's network subnet and both are different:

Home network subnet: is 192.168.0.X
VPN network subnet: is 192.168.1.X
Subnet mask is: 255.255.255.0

Additionally, I disabled the firewall in my router with no help. What else I can do.

Case:

Assume I have a site hosted in server with IP: 192.168.1.50. From my local network, I can ping the server after connecting to VPN but I cannot browse the site using http://192.168.1.50 or sftp to 192.168.1.50.

Update

Here is the result after running tracert -c 192.168.1.50:

Tracing route to 192.168.1.50 over a maximum of 30 hops

  1    18 ms    12 ms    19 ms  10.8.0.1
  2    13 ms    20 ms    12 ms  192.168.1.50

Trace complete.

server route info:

0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eno1
172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0
172.25.0.0      0.0.0.0         255.255.0.0     U     0      0        0 br-8730262616cd
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eno1

Wireshark:

I installed and ran wireshark in my local PC and tried to call server with IP 192.168.1.150. After connecting to VPN, I was assigned IP 10.8.0.10. The handshake and TLS was successful but wireshark gave a warning on the last TCP exchange:

It might be a MTU issue. Try to set your VPN Tunnel NIC MTU to e.g. 1420. This kind of issue happen if you're using Packetencapsulation e.g. in IPSec

https://www.cisco.com/c/en/us/td/docs/interfaces_modules/services_modules/vspa/configuration/guide/ivmsw_book/ivmvpnb.pdf

It is unclear if you are pinging from remote PC you RDP'd to, or from your home-PC. -I am assuming you pinged from remote PC. You have a connection to the remote PC so either the remote PC has a route entry that points back to your home network, or the servers have route entries that points to a different 192.168.0.X network than yours. -When you try to connect to them, you are probably reaching them, but the servers do not know how to connect back to your PC.