ok. If you can get a page locally, you should notice the URL used. The port used should be a part of the URL. This is the port used by owncloud, and this is the one which must be forwarded from outside to your NAS in order to get access from outside.
You need then to construct the "from the outside" URL : your public IP address ( or DNS if you have one ) + the same port you got locally.
ownCloud: Trying and Failing
-
- Posts: 395
- youtube meble na wymiar Warszawa
- Joined: Tue Aug 25, 2015 9:23 pm
-
- Posts: 917
- Joined: Fri May 15, 2015 1:56 am
Re: ownCloud: Trying and Failing
Or you can do as I suggested and we sort of talked about on the phone... Using another port from the outside going to the inside port. This gives an extra layer of protection, as most hackers scan commonly used ports, and don't go out to scan all 65K+ ports for each IP... It would take too long.
So, as per sksbir's suggestion, from the WAN on port xxxxx to the LAN on port (the same port you have for local IP's.)
This doesn't CURE or PREVENT a hacker from getting in, it just makes it harder for one to do so.
So, as per sksbir's suggestion, from the WAN on port xxxxx to the LAN on port (the same port you have for local IP's.)
This doesn't CURE or PREVENT a hacker from getting in, it just makes it harder for one to do so.
-
- Posts: 26
- Joined: Tue Feb 02, 2016 11:31 pm
Re: ownCloud: Trying and Failing
This is what I get when trying to log in off-site. And if I trust it, nothing good happens, connection drops.
-
- Posts: 395
- Joined: Tue Aug 25, 2015 9:23 pm
Re: ownCloud: Trying and Failing
- did you started your web server only in https mode ?
- you must adjust config.php ( stored in /share/Web/owncloud/config from ssh terminal, or from "Web" shared folder from file explorer ) to authorize the use of the URL you use from the outside. See the "trusted_domains" keyword
. in the URL, you must have the "owncloud" keyword, eg : https://xxxxx:port/owncloud/
- In order NOT to have "owncloud" in your URL path, I recommend you to create a virtual host on a specific port , with https protocol, and with /Web/owncloud has folder name
ADM --> service --> web server --> virtual host.
You must forward this new specific port to your NAS, after that, URL becomes something like https://xxxx:yyy , with yyy = specific port.
To know more about owncloud installation : https://doc.owncloud.org/server/8.0/adm ... tents.html
- you must adjust config.php ( stored in /share/Web/owncloud/config from ssh terminal, or from "Web" shared folder from file explorer ) to authorize the use of the URL you use from the outside. See the "trusted_domains" keyword
. in the URL, you must have the "owncloud" keyword, eg : https://xxxxx:port/owncloud/
- In order NOT to have "owncloud" in your URL path, I recommend you to create a virtual host on a specific port , with https protocol, and with /Web/owncloud has folder name
ADM --> service --> web server --> virtual host.
You must forward this new specific port to your NAS, after that, URL becomes something like https://xxxx:yyy , with yyy = specific port.
To know more about owncloud installation : https://doc.owncloud.org/server/8.0/adm ... tents.html
-
- Posts: 917
- Joined: Fri May 15, 2015 1:56 am
Re: ownCloud: Trying and Failing
GODS, I'm sorry, I forgot all about having to do that step. It's been almost 2 years since I set up ownCloud, and forgot I had to edit the config.php. Good catch sksbir!
I hope everything works now, Gramotey?
I hope everything works now, Gramotey?
-
- Posts: 26
- Joined: Tue Feb 02, 2016 11:31 pm
Re: ownCloud: Trying and Failing
Gentlemen, thank you. Just a quick reply... I am swamped and tired. Tomorrow I'll elaborate more, but in a barebone sense, it finally works. I'll have to kill it and do from scratch now, and do it right, and then document the steps. HTTPS isn't working, too tired to try and solve now... but without your help MikeG.6.5 and sksbir, I'd not move this project at all... Thank you!