Ramboxman
Explorer
- Joined
- Jun 20, 2013
- Messages
- 63
I noticed now I need to always have a keyboard attaced to server or else system will hang on restart is this normal. I never had a keyboard plugin in prior to 9.3 unless I needed to.
Transfer speeds are consistly 20-30 faster for me, have no idea what changed to cause this. I am getting 70 -75 mb/sec with an atom processor see my system specs in signature. Anyone else notice this.
Bty- upgrade failed. reinstalled for iso and imported configuration and had the CSRF issues access webgui (appartently I had https enabled see bug #7049.I then SSH-ed in and edited:
The patch is changing following line in /etc/local/rc.d/django
from:
if [ ${webguiproto} = "https" ]; then
to:
if [ ${webguiproto} = "https" -a ! -f /tmp/alert_invalid_ssl_nginx ]; then
Once modified and django restarted using "./django restart" (needing twice for some reason) I could login using HTTP.
As per 5.9. CAs, I created internal CA (System->CA) and then internal Certificate (System->Certificates) referencing forementioned internal CA; then changed Protocol to HTTPS (System ->General : Protocol) and rebooted.
Now can login using HTTPS. (Browser will complain because certificates is signed by non-trusted CA - you'll need to tell it to create an exception).
You can edit it with the shell directly on your NAS, or by ssh.
Follow ALL the steps:
1. log in (ssh or shell)
2. type " edit /etc/local/rc.d/django "
3. change the text as above "https" ]; then to "https" a ! -f /tmp/alert_invalid_ssl_nginx ]; then
4. save it esc+enter
5. type " cd /etc/local/rc.d/ "
6. type " ./django restart "
7. type " ./django restart " yes twice
8. log in your nas http://you.local.nas.address
9. go to system
10. system ->CA create a CA
11. system> certificates create a certificate
12. system -> general chose the certificate you just did
Transfer speeds are consistly 20-30 faster for me, have no idea what changed to cause this. I am getting 70 -75 mb/sec with an atom processor see my system specs in signature. Anyone else notice this.
Bty- upgrade failed. reinstalled for iso and imported configuration and had the CSRF issues access webgui (appartently I had https enabled see bug #7049.I then SSH-ed in and edited:
The patch is changing following line in /etc/local/rc.d/django
from:
if [ ${webguiproto} = "https" ]; then
to:
if [ ${webguiproto} = "https" -a ! -f /tmp/alert_invalid_ssl_nginx ]; then
Once modified and django restarted using "./django restart" (needing twice for some reason) I could login using HTTP.
As per 5.9. CAs, I created internal CA (System->CA) and then internal Certificate (System->Certificates) referencing forementioned internal CA; then changed Protocol to HTTPS (System ->General : Protocol) and rebooted.
Now can login using HTTPS. (Browser will complain because certificates is signed by non-trusted CA - you'll need to tell it to create an exception).
You can edit it with the shell directly on your NAS, or by ssh.
Follow ALL the steps:
1. log in (ssh or shell)
2. type " edit /etc/local/rc.d/django "
3. change the text as above "https" ]; then to "https" a ! -f /tmp/alert_invalid_ssl_nginx ]; then
4. save it esc+enter
5. type " cd /etc/local/rc.d/ "
6. type " ./django restart "
7. type " ./django restart " yes twice
8. log in your nas http://you.local.nas.address
9. go to system
10. system ->CA create a CA
11. system> certificates create a certificate
12. system -> general chose the certificate you just did