I’m using Windows 10 and have chosen the Appliance variant of Owncloud have installed everything like Virtualbox virtualmachine, uploaded regfile to the desktop client, have got access to admin account etc. But there is very little information what I can see, about using the software in windows environment.
How do I share folders on local harddisk in windows? What about this “external filesharing” not being enabled?
How do I connect to my host computer from the outside, the computer hosting the server is connected through a router, which ports to forward? Do I connect to the VMs ip adress or the computers ip?
Thanks for answer, but I have read all those docs and nothing comes close to helping me. First of all, I can’t connect to the server other than from the same computer with the 192.168.x.xx local ip. I can’t with my android phone and not with the desktop client, only web client. In what way must I type in the adress in the desktop client?
Once again - networking issue, now ownCloud issue.
If you have the appliance set up locally, it has a private IP. This can not be routed = no access from outside your routers network. Basic networking knowledge.
If you have a router, with a static IPv4 address, you can forward the port 80 for HTTP or port 443 for HTTPS (if you have HTTPS configured and enabled + valid certificates) on your router to access the ownCloud server.
What to type in your Phone or Sync client? The address of your server.
Example: my appliance is running under
That’s what I type in in my sync client and I can connect to my ownCloud, enter username and password for an account I have there and start syncing.
I tried installing it on my home pc without any routers and stuff like that, pure ethernet connection from wall, and now the desktop client nags about certificates and security issues. How didnt you get any of this?
I managed to get it to work, here is how I did it.
You have to set " App passwords / tokens" in the Security tab in Owncloud webclient settings, and use this with the desktop client to get access, now where do you state this? Nowhere, I had to figure it out myself.
You have to use the external IP when connecting, AND you MUST put it in this form “https://37.46.xxx.xx/owncloud” otherwise it wont work, where do you state this? Nowhere.
You should update your installation instructions for this software, as all people present on the internet are not Linux geeks or IT-Engineers/Network specialists.
This is strange. What errors have you fixed by doing this?
When you start the appliance there is a blue windows, which tells you what to type in your browser, right?
Then, if you click on the ownCloud icon in the Portal, you get redirected. The Address changes to what you posted, and what I posted earlier, right?
Where is the surprise? What were you expecting?
First - you should not speak so negatively. If you want people to help you - show some interest, show that you googled for yourself, made yourself familiar with the thing you are asking about.
Yelling in to this forum “IT DOES NOT WORK!” and having a negative attitude won’t get you the result you desire.
Second - we are open to feedback - So where would you have been expecting / missing the information you found by yourself? Can you point me to a site where this information should be added?
There is no explanation how to SPECIFICALLY insert server adress, its highly sensitive and must include full strings with “https”, “/owncloud” etc.
I’m sure it’s mandatory to tick the box with “App Passwords/Tokens”, it was needed to enter the temporary password received here in the desktop client to initially gain access. Where is this mentioned in the manuals avaliable?
What about the certificate error that ruins your day when its time to input password/username when connection is successful after the step above? How many amateur/semi-experienced users would just ignore this? Where is the statement for this issue and how to resolve it during first connect?
This software appears to be to good to be primary targeting a fringe group like Elite Hackzor Linux users and enterprise IT-guys that fixes stuff by themselves trough experience and trial-and-error.
You should always browse the web via https. Right?
Okay, the next thing is more complicated. But I try to explain it.
The /owncloud makes sense if you think about it. You have a server, right?
On that server you can have multiple applications, right? How would you access them?
You know that your server is on 192.168.178.1, right?
But you installed ownCloud and nextcloud. How would you tell your browser - Go to ownCloud? Well, you need a name what you can call. This is specified in your apache configuration.
You specify that if you enter your server address and /owncloud you will access ownCloud and /nextcloud will take you to nextcloud.
Honestly? It’s the first time I am hearing this. I have installed ownCloud 100s of times for testing and never did I run in to the problem you are describing. If you could provide steps to reproduce, I will try to reproduce it and get to the source of this issue.
surely you can understand that security is a high priority issue for ownCloud.
There is a guide how to get good certificates in the installation section of the documentation:
But my top question right now is - what manual / doc were you using and where would you expect improvement: what page what place and how. all this you can formulate and post in an issue on github https://github.com/owncloud/docs/issues or write it here and I will do it.
Thanks for the answers but as I found the OwnCloud software to be to immature and sensitive for my taste I did setup my own FTP server, available trough website and picture autoupload from phone via MEGAsync. If you just about sneeze near your computer OwnCloud wouldn’t connect anymore and you had to visit the router admin pages for the millionth time and you had to start digging in forwarding ports, googling certificate issues, firewall issues etc all over again. No thanks. OC is as of now targeting a cringe group of users and is not ready for the broad masses yet, will revisit the software in the future.