Media playback is one of it's (raspi) jobs at home. I have a few. In the car, good idea.
Have a nice weekend. Hear you perhaps sometimes later again.
Thank you for help.
rasonprof
Posts by rasonprof
-
-
Hi steel2400,
the raspi is more a toy for me, I check what it can do for me. To use it as a small server or nas it has to much limitations. For example USB, and Network throughput at the other hand he has a real low power consumption.
Apache I've checked at first. It doesn't run.
Believe it there were to much errors. Therefore I decided to reinstall OMV and then to consider whether the error messages of the two configuration files (.conf
come, when I restart nginx and I want to see what I did before the problem occurred, in case it should occur again, and perhaps if I have a lot of luck it no longer occurs. If I will see something inside the new .conf files, I'll come back again.I've had a few issues with OMV. I could fix nearly all. Sometimes by an try and error method.
I will come back after the new installation, but it can take a bit of time.
Best Regards
rasonprof
-
Hi steel2400,
the reason for ssl is that I'm using Owncloud mainly from outside. Usually I do this by an open VPN connection. But as fallback, perhaps openVPN is crashed, I have the dyn accout with a different port no. from the OMV internal. This port in the outgoing router is usually closed and I open it if I need it and for such connections I work with ssl and why should I change between http and https, if I work with tunnelor not. So I have allways https. That is the main intention.
Now to the problem itself. I have done what you've said. I got so much errors after re-installation of nginx and nothing happens after trying to connect that I think it's better to re-install OMV completely. But now I've seen that there is a new raspi image and the OMV 2.1 path in the download section is deleted. My question is, are there so much errors in that image that they hold it back and do a bit more polish it. I don't know it. But I will look, what will be happend inthe download section and than start a new trial.
Ah I forgot, I've had a look for the path of nginx and I mean It should be complete.
rasonprof
-
Good Morning,
you are right, I prefer the ssl connection. But, inside the other Installation which was disappearing, I was working with forced ssl connection. Inside this one both is possible, http and https. Port 80 isn't be shown, because nginx isn't running.
Today afternoon, I'll reinstall nginx. I haven't made it before, because I was hoping to solve it without reinstallation.
rasonprof
-
Hi,
me again.
I've compared the output with my raspi OMV installation and the related ports which I'm missing belong to nginx, which is not running in this installation. Now we have only to clarify why it's not running and why it is silently disappearing. For the moment a safe installation of OMV, on this machine, is impossible for me, because this happens two times.
rasonprof
-
Hi,
here I've made a mistake, before I've only checked the missing ports with netstat -tulpn grep (portno) and not the whole range.
Below I send the output of netstat -tulpn. The usually used ports, within my installation, of owncloud (8443) and OMV GUI (9443, i've changed it) are missing.Aktive Internetverbindungen (Nur Server)
Code
Display MoreProto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:904 0.0.0.0:* LISTEN 3321/python tcp 0 0 0.0.0.0:8200 0.0.0.0:* LISTEN 2349/minidlnad tcp 0 0 127.0.0.1:905 0.0.0.0:* LISTEN 3321/python tcp 0 0 127.0.0.1:906 0.0.0.0:* LISTEN 3321/python tcp 0 0 127.0.0.1:907 0.0.0.0:* LISTEN 3321/python tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 3274/smbd tcp 0 0 127.0.0.1:908 0.0.0.0:* LISTEN 3321/python tcp 0 0 127.0.0.1:3308 0.0.0.0:* LISTEN 3105/mysqld tcp 0 0 127.0.0.1:909 0.0.0.0:* LISTEN 3321/python tcp 0 0 172.27.50.254:943 0.0.0.0:* LISTEN 3321/python tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1959/rpcbind tcp 0 0 0.0.0.0:32400 0.0.0.0:* LISTEN 3197/Plex Media Ser tcp 0 0 0.0.0.0:32401 0.0.0.0:* LISTEN 3197/Plex Media Ser tcp 0 0 0.0.0.0:1076 0.0.0.0:* LISTEN 3404/Plex DLNA Serv tcp 0 0 0.0.0.0:32469 0.0.0.0:* LISTEN 3404/Plex DLNA Serv tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 3300/sshd tcp 0 0 127.0.0.1:3350 0.0.0.0:* LISTEN 2353/xrdp-sesman tcp 0 0 0.0.0.0:631 0.0.0.0:* LISTEN 3129/cupsd tcp 0 0 0.0.0.0:51768 0.0.0.0:* LISTEN 3314/Plex Plug-in [ tcp 0 0 0.0.0.0:42586 0.0.0.0:* LISTEN 1977/rpc.statd tcp 0 0 127.0.0.1:2812 0.0.0.0:* LISTEN 3598/monit tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 3274/smbd tcp 0 0 0.0.0.0:3389 0.0.0.0:* LISTEN 2340/xrdp tcp6 0 0 :::139 :::* LISTEN 3274/smbd tcp6 0 0 :::111 :::* LISTEN 1959/rpcbind tcp6 0 0 :::22 :::* LISTEN 3300/sshd tcp6 0 0 :::631 :::* LISTEN 3129/cupsd tcp6 0 0 :::35255 :::* LISTEN 1977/rpc.statd tcp6 0 0 :::445 :::* LISTEN 3274/smbd udp 0 0 0.0.0.0:631 0.0.0.0:* 3129/cupsd udp 0 0 0.0.0.0:862 0.0.0.0:* 1959/rpcbind udp 0 0 127.0.0.1:881 0.0.0.0:* 1977/rpc.statd udp 0 0 172.27.50.254:1194 0.0.0.0:* 3370/openvpn-openss udp 0 0 0.0.0.0:5353 0.0.0.0:* 3074/avahi-daemon: udp 0 0 172.27.50.254:38553 0.0.0.0:* 3197/Plex Media Ser udp 0 0 0.0.0.0:1900 0.0.0.0:* 3404/Plex DLNA Serv udp 0 0 239.255.255.250:1900 0.0.0.0:* 2349/minidlnad udp 0 0 0.0.0.0:51257 0.0.0.0:* 3404/Plex DLNA Serv udp 0 0 127.0.0.1:43158 0.0.0.0:* 3197/Plex Media Ser udp 0 0 0.0.0.0:35029 0.0.0.0:* 1977/rpc.statd udp 0 0 0.0.0.0:52305 0.0.0.0:* 3404/Plex DLNA Serv udp 0 0 172.27.50.254:56507 0.0.0.0:* 2349/minidlnad udp 0 0 0.0.0.0:52722 0.0.0.0:* 3074/avahi-daemon: udp 0 0 0.0.0.0:32410 0.0.0.0:* 3197/Plex Media Ser udp 0 0 0.0.0.0:32413 0.0.0.0:* 3197/Plex Media Ser udp 0 0 0.0.0.0:32414 0.0.0.0:* 3197/Plex Media Ser udp 0 0 172.27.224.1:44905 0.0.0.0:* 2349/minidlnad udp 0 0 0.0.0.0:111 0.0.0.0:* 1959/rpcbind udp 0 0 172.27.50.255:137 0.0.0.0:* 3271/nmbd udp 0 0 172.27.50.254:137 0.0.0.0:* 3271/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 3271/nmbd udp 0 0 172.27.50.255:138 0.0.0.0:* 3271/nmbd udp 0 0 172.27.50.254:138 0.0.0.0:* 3271/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 3271/nmbd udp 0 0 0.0.0.0:8406 0.0.0.0:* 3404/Plex DLNA Serv udp 0 0 127.0.0.1:57833 0.0.0.0:* 3197/Plex Media Ser udp 0 0 172.27.50.254:45558 0.0.0.0:* 3197/Plex Media Ser udp6 0 0 :::862 :::* 1959/rpcbind udp6 0 0 :::5353 :::* 3074/avahi-daemon: udp6 0 0 :::42984 :::* 1977/rpc.statd udp6 0 0 :::111 :::* 1959/rpcbind udp6 0 0 :::45227 :::* 3074/avahi-daemon:
Best Regardsrasonprof
-
Hi,
I've made a stop/start of nginx a few days a go. There I got an error message, but an error must not mean that the service isn't up. Below you can find this message and the related conf files. Sorry, I don't know what could be wrong. According to your proposal with /etc....../nginx reload, I have made it and I got the same message. Then I've made a /etc...../nginx status, and I receive the message that nginx isn't running. My question is why. I never change something inside the related conf files which are shown below. I will compare it with the older OMV version on my raspi. Perhaps I'm be able to find something. There is a second thing, which I don't understand, the WebGUI of Plex and openVPN AS (client site to download the client software)is reachable.
"Reloading nginx configuration: nginx: [emerg] invalid number of arguments in "proxy_set_header" directive in /etc/nginx/openmediavault-webgui.d/sub.conf:4
nginx: configuration file /etc/nginx/nginx.conf test failed"Code
Display Moresub.conf (start) location /subsonic { proxy_pass [url]http://localhost:4040/subsonic[/url]; #proxy_set_header Host localhost:4040; proxy_set_header Host ; proxy_redirect default; } sub.conf (end) nginx.conf (start) user www-data; worker_processes 4; pid /var/run/nginx.pid; events { worker_connections 768; # multi_accept on; } http { ## # Basic Settings ## sendfile on; tcp_nopush on; tcp_nodelay on; keepalive_timeout 65; types_hash_max_size 2048; # server_tokens off; # server_names_hash_bucket_size 64; # server_name_in_redirect off; include /etc/nginx/mime.types; default_type application/octet-stream; ## # Logging Settings ## access_log /var/log/nginx/access.log; error_log /var/log/nginx/error.log; ## # Gzip Settings ## gzip on; gzip_disable "msie6"; # gzip_vary on; # gzip_proxied any; # gzip_comp_level 6; # gzip_buffers 16 8k; # gzip_http_version 1.1; # gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml$ ## # nginx-naxsi config ## # Uncomment it if you installed nginx-naxsi ## #include /etc/nginx/naxsi_core.rules; ## # nginx-passenger config ## # Uncomment it if you installed nginx-passenger ## #passenger_root /usr; #passenger_ruby /usr/bin/ruby; ## # Virtual Host Configs ## include /etc/nginx/conf.d/*.conf; include /etc/nginx/sites-enabled/*; } #mail { # # See sample authentication script at: # # [url]http://wiki.nginx.org/ImapAuthenticateWithApachePhpScript[/url] # # # auth_http localhost/auth.php; # # pop3_capabilities "TOP" "USER"; # # imap_capabilities "IMAP4rev1" "UIDPLUS"; # # server { # listen localhost:110; # protocol pop3; # proxy on; # } # # server { # listen localhost:143; # protocol imap; # proxy on; # } #} nginx.conf (end)
I hope I forgot nothingrasonprof
-
Hello all,
I have the problem that my OMV installation has lost the Web GUI connection. This is happen the second time. The first I've played with the installation and so I thought that I've made something wrong. Because suddenly no connection was possible, neither to OMV nor to owncloud. I've made a new installation and after a few days the same, I restart my server a then no Web access to OMV and owncloud.
The connection to openVPN AS by Web access is possible. Two installed shares (two are active) seem to be working. Plex Web access is working, but there is no connection between owncloud client and server and no web access to owncloud and OMV. I've made a portscan and all related ports are closed. I've made the portscan direct to the server without router between to exclude a faulty router.
I forgot, SSH is possible to. I'made an upgrade to 2.1.1 by SSH connection, hoping that the new version will bring back the connection but nothing happens. I've restarted ngingx, but nothing happens. I've read that this was happened in older versions too.
It is easy for me to do a new installation, but this can't be the solution for the future I think.
Do you have an idea what it could be? The hardware is an HP proliant N40L
Thanks in advance
rasonprof