I managed to get everything set-up perfectly
fine. I have seafile and seahub running, and able to access
browser on PC, laptop, and mobile. Both Windows and Android client apps
work. It’s also insanely faster compared to what I was able to achieve
However, for some reason it is incredibly slow or completely
non-responsive when trying to access seafile from a WAN connection. I
have both 8001 and 8082 ports forwarded (set the config in seafile to 8001 as 8000 is already taken by Wallabag) to the device running seafile.
The majority of the time I get a ‘connection timed out’ error page in my
browser when trying to access seafile. If the connection does not time
out I can sometimes manage to log in but get a ‘permission error’ when
trying to access any libraries. Given this happens after a long time, I
am guessing it’s a case of the connection timing out again. On the
Android device I get ‘Error when loading folder’, again likely due to
connection timing out. Strangely, for some reason whilst seafile tries
to load all my other services are inaccessible as well until the seafile
connection times out - even the services that are running on different
devices but only share the domain through port forwarding.
Any ideas what I could be doing wrong or need to change to fix this?
(Apologies for cross-posting this from the other forum - didn’t realise there were separate German and English forums!)