Beiträge von perler

Ha! a typo! nice, thanks.

I connect some esxi server to OMV via NFS. I did this before with openfiler, worked flawless. in principle it works as well or better with OMV - but as son as I enable the firewall, a df (or any other "checking" of the filesystems) in esxi is very slow (+120 sec). the speed of the NFS storage itself is fine.

my firewall rules are such, that 110 and 2049 and 4045 TCP/UDP are allowed as well as that I completely allow all traffic between OMV and ESXi hosts.

have a look: http://screencast.com/t/Oak7WBtPM

I start the firewall, start df, wait, then I clear the firewall and immediately df returns results.

issue reportet.

ok, but as the plugin doesn't really work without manually enabling the "external storage" app, should this be considered a bug? is there a place to report it?

ok, this works for settings that go directly into config.php - what about permanently enabling/diabling apps. how can we make this permanent?

the owncloud plugin looks a bit abandoned - so I wonder, is there a way to add some extra options into the owncloud config file (config.php)? this is neccessary for getting the whole folder integration working (as it needs support for external storage) and also for proxying through nginx (and a thousand other things I'm sure).
right now, whatever I enter get's overwritten as soon as you add a folder..

re #3:

the command line interface: http://manual.calibre-ebook.com/cli/ebook-convert.html
someone tried this in python: http://pastebin.com/XdPZUdpg
and explains it here: http://www.mobileread.com/forums/showthread.php?t=142093

I didn't get the python script to work..

Ok, I see, thanks!

Is the Directory Service here: http://screencast.com/t/8OOQfTiMG a full fledged LDAP server, that can be used for other things too?

I don't seem to be able to connect to it from the outside. where are the config fles or what type of LDAP server is it?

is the calibre plugin still in acive development? I really would likte to see

• monitoring of the input directory (can be a cron job every x minutes)
• filtering, what get's imported (right now every .txt file is imported, for instance)
• conversion while importing (if epub, convert to mobi and the other way around)

the command line of calibre is able to do this, would be nice to have it in the backend..

Did some reading. We can accomplish this quite easiyly right now by haveing two domains with the same name, one listening on 443 (but not on 80), delivering the content and one listening on 80 (but not on 443) wth the opton

return         301 https://$server_name$request_uri;

in the Extras option field.

Maybe you can implement an option for this?

ok, just to clearify, is there a way to actually enforce ssl ina way, that whoever accesses http://sub.domain.com:80 gets redirected to https://sub.domain.com:443

this prevents an nginx restart with

root# /etc/init.d/nginx restart
Restarting nginx: nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] bind() to 0.0.0.0:443 failed (98: Address already in use)
nginx: [emerg] still could not bind()
nginx.

the ../openmediavault-nginx after adding the line to the extra options looks like this:

server {
    listen [::]:443 ssl;
    ssl_certificate     /etc/ssl/certs/openmediavault-8a8f2078-f1bc-4fa7-a344-108502e2225c.crt;
    ssl_certificate_key /etc/ssl/private/openmediavault-8a8f2078-f1bc-4fa7-a344-108502e2225c.key;
    server_name sub.domain.com;
    index index.html;
    access_log /var/log/nginx/6a9d3536-4ab8-4a3b-aed8-4387787873a9-access.log;
    error_log  /var/log/nginx/6a9d3536-4ab8-4a3b-aed8-4387787873a9-error.log;
    large_client_header_buffers 4 8k;
    location / {
        proxy_pass http://localhost:8080;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;........
    }
listen 443 ssl;


}

../openmediavault-webgui

server {
    server_name openmediavault-webgui;
    root /var/www/openmediavault;
    index index.php;
    autoindex off;
    server_tokens off;
    sendfile on;
    large_client_header_buffers 4 32k;
    client_max_body_size 25M;
    error_log /var/log/nginx/openmediavault-webgui_error.log error;
    access_log /var/log/nginx/openmediavault-webgui_access.log combined;
    location /extjs/ {
        alias /usr/share/javascript/extjs4/;
    }
    location /images/ {
        alias /var/www/openmediavault/images/;
    }
    location ~ \.php$ {
        try_files $uri = 404;
        fastcgi_split_path_info ^(.+\.php)(/.+)$;
        fastcgi_pass unix:/var/run/php5-fpm-openmediavault-webgui.sock;
        fastcgi_index index.php;
        fastcgi_read_timeout 60s;
        include fastcgi_params;
    }
    listen [::]:80 default_server ipv6only=off;
    listen [::]:443 default_server ipv6only=off ssl deferred;
    ssl_certificate /etc/ssl/certs/openmediavault-8a8f2078-f1bc-4fa7-a344-108502e2225c.crt;
    ssl_certificate_key /etc/ssl/private/openmediavault-8a8f2078-f1bc-4fa7-a344-108502e2225c.key;
    include /etc/nginx/openmediavault-webgui.d/*.conf;
}

example from ../openmediavault-nginx

server {
    listen [::]:443 ssl;
    ssl_certificate     /etc/ssl/certs/openmediavault-8a8f2078-f1bc-4fa7-a344-108502e2225c.crt;
    ssl_certificate_key /etc/ssl/private/openmediavault-8a8f2078-f1bc-4fa7-a344-108502e2225c.key;
    server_name proxiedsite.domain.com;
    index index.html;
    access_log /var/log/nginx/6a9d3536-4ab8-4a3b-aed8-4387787873a9-access.log;
    error_log  /var/log/nginx/6a9d3536-4ab8-4a3b-aed8-4387787873a9-error.log;
    large_client_header_buffers 4 8k;
    location / {
        proxy_pass http://localhost:8080;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }


}

that's how it is set up:

OMV: https://omv.domain.com:443
nginx proxy: https://calibre.domain.com:443 (but set up, that requests to http://calibre.domain.com:80 should be served from https://calibre.domain.com:443)

all the name based servers created with the "websites (nginx) " plugin are listening to 443, but don't seem to have the

listen [::]:80;

statement - isn't that neccessary to force SSL?

in the websites (nginx) plugin you have the option to force a website to SSL. I want to use this as a method to proxy to unsafe sites, but whenever I try to access http://test.domain.com, instead of enforcing https://test.domain.com the OMV admin panel appears.

what can we do here?

ok. this looks all very strange and to be related to the very persistent cache of google chrome. after diabling https, even after clsing opening and opening a private browsing session, it redirected http to https. cleaning the cache for the last day didn't anthing, just after cleaning the whole browser cache I could access the http part of OMV and after re-enabling https access, all the other problems disappeared.

strange.

please ignore, this is seems to be the reason: OMV web interface redirects to https although https-redirect is disabled

(please ignore thread all plugin web interfaces redirect to https and post openmediavault-nzbget plugin - this here seems to be the reason for both problems)

I tried to disable https access to the web interface for testing purposes, but, alhough the webinterface at 443 is disabled, nginx redirects all requests to https://server:443.

This happended some time ago, could be related to a plugin, but I'm not sure. any ideas, at least to re-enable the web interface at 443 for now, but, mainly to get rid of this darn redirect?!

after installing and pressing the button to open the web interface I get redirected not to http://server:6789 but to https://server:6789 - can you think of a reason why? it happens with other plugins too, I must say..

please ignore, this seems to be the reason: OMV web interface redirects to https although https-redirect is disabled - the mod can delete this entry if he feels like it.