Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. ![]()
The Basics
- Nextcloud Server version (e.g., 29.x.x):
- Nextcloud Hub 25 Autumn (32.0.6)
- Operating system and version (e.g., Ubuntu 24.04):
- Ubuntu Linux 24.04.4
- Web server and version (e.g, Apache 2.4.25):
- Apache version 2.4.58
- Reverse proxy and version _(e.g. nginx 1.27.2)
none
- PHP version (e.g, 8.3):
- 8.3.30
- Is this the first time you’ve seen this error? (Yes / No):
yes
- When did this problem seem to first start?
replace me
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
replace me
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
no
Summary of the issue you are facing:
After update from nextcloud 32.0.5.0 nach 32.0.6.1 My Files Folder ist not available
Steps to replicate it (hint: details matter!):
Log entries
Among others:
File access/syncing broken: ‘TypeError fsockopen(): Argument #2 ($port) must be of type int, string given’
Searching for this led to
and in it the links to
[Bug]: Upgrade to 32.0.6 breaks existing SFTP connections with custom ports · Issue #58293 · nextcloud/server · GitHub and
The solution was then simple for me:
I had to re-establish the SFTP connection to the external storage and specify port 22. The error is gone.
Maybe it will help someone.