Jump to content

CyberMew

Members
 View Profile  See their activity

  • Posts

    410

  • Joined

 Content Type 

Posts posted by CyberMew

    Data rebuild with errors?

    in General Support

    Posted · Edited by CyberMew
    add syslog

    Hi, some backstory. I added a new disk8 and was clearing it when the connection on my disk1 died, so I didn't format disk8 and wanted to shutdown the server to fix disk1 connection.

     

    After I managed to fixed it (apparently the cable died for some reason), it prompted for a data rebuild (even though i dont think it was required).

     

    Now, while it went through the parity check/data rebuild process, it seems like several health issues on various drives popped up. Disk 2 had a 

    Current pending sector count of 1 but 0 reallocated event count (it didn't grow further though). Disk 7 also had its udma crc error count grow from 4 to 10 (I am going to try to replace this sata cable with a new one).

     

     

    The data rebuild was complete but with 54 errors! Does it mean some parts of the data was not restored? Or does it mean the parity drive was updated?

    I'm a bit worried here.. usually it's 0 errors.

     

    Attached logs.

    tower-diagnostics-20190915-1235.zip

    tower-syslog-20190915-1251.zip

    SSD cache drive no longer accessible.

    in General Support

    Posted

    Thanks, pretty sure it's already screwed down tight a couple months ago, but will still double check the screw in case it somehow came loose. 

     

    So far it's been running for 24 hours and all seems to be fine 🤞Let's see what happens during the next parity check next month..that's when the read/drive errors will usually appear again

    SSD cache drive no longer accessible.

    in General Support

    Posted · Edited by CyberMew

    It went down 12 hours ago and i'm not sure why.. only discovered it went down when the docker containers werent running and said something about a readonly file system (cache).

     

    This is a 2 month old ssd drive and it was working fine all along.

     

    Attached a copy of the syslog (red logs are all the way down) and diagnostics.

     

    I have stopped my docker service. Should I shutdown my server as well?

    tower-syslog-20190721-0314.zip tower-diagnostics-20190721-0317.zip

    [Support] Linuxserver.io - OpenVPN AS

    in Docker Containers

    Posted · Edited by CyberMew

    6 hours ago, dajinn said:

    Go into your Access Server settings and change the hostname from the docker IP to your public IP/hostname.

    Thanks! Working fine, able to connect now! Now I just need to find out why my new nonadmin users don't have a cert (client cert revoked) and fix it.. edit: worked by itself after a while. all good

    [Support] Linuxserver.io - OpenVPN AS

    in Docker Containers

    Posted · Edited by CyberMew
    help required

    How do we connect to the docker from iOS OpenVPN Connect app? I selected Access Server and put in the details but it isnt working. Edit: needed to provide 9443 in port field.

     

    Edit 2: why is it connecting to my docker internal ip 172.17.x.x:1194?

    [Support] Linuxserver.io - OpenVPN AS

    in Docker Containers

    Posted

    21 hours ago, CHBMB said:

    But that shows it running? Can you not get to the webui.

    Sent from my Mi A1 using Tapatalk
     

    Ah yes it's working now, I guess I tried it while it was still loading up.

     

    I just realise that it's limited for 2 connections? I remember it was totally free and open source?

    Dynamix - V6 Plugins

    in Plugin Support

    Posted 

    Model: N/A
M/B: Micro-Star International Co., Ltd. - X470 GAMING PRO CARBON (MS-7B78)
CPU: AMD Ryzen 7 2700 Eight-Core @ 3200
HVM: Enabled
IOMMU: Enabled
Cache: 768 kB, 4096 kB, 16384 kB
Memory: 32 GB (max. installable capacity 256 GB)
Network: bond0: fault-tolerance (active-backup), mtu 1500 
 eth0: 1000 Mb/s, full duplex, mtu 1500
Kernel: Linux 4.18.20-unRAID x86_64
OpenSSL: 1.1.1a
Uptime: 3 days, 01:52:06

    After installing and clicking on Detect, it does nothing. Is this still working on v6.6.7 or on amd chips?

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    On 9/11/2018 at 1:45 AM, aptalca said:

    Post what you have. Either pastebin or screenshots where necessary. 

     

    And also, are you going to https://ombi.domain.com ? 

    Yes I'm going to that url (where domain is my own domain).

     

    Currently I'm trying this: 

    server {
	listen 80;
	server_name _;
    rewrite     ^   https://$host$request_uri? permanent;
}

server {
	listen 443 ssl;

	root /config/www;
	index index.html index.htm index.php;

	# Replace domain.com with my own domain
	server_name ombi.domain.com;

	# Removed just in case this is sensitive
	ssl_certificate LOCATION_REDACTED;    
	ssl_certificate_key LOCATION_REDACTED;    
	ssl_dhparam LOCATION_REDACTED;    
	ssl_ciphers 'CIPHER_REDACTED';
	ssl_prefer_server_ciphers on;

	add_header Strict-Transport-Security "max-age=31536000";


	client_max_body_size 0;

	location / {
		auth_basic off;    
		auth_basic_user_file /config/nginx/.htpasswd;
		include /config/nginx/proxy.conf;
		proxy_pass http://192.168.1.55:12345;	
	}
}

     

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    On 9/9/2018 at 5:47 AM, aptalca said:

    I think you're confused about how webservers and reverse proxy works. 

     

    You port forwarded 12345 directly to the container's gui. So if you go to domain:12345 you connect directly to the container's gui. It does not go through nginx.

     

    With that config, nginx is listening on port 443 so you have to go to https://domain:443 or you can just go to https://domain because 443 is the default https port, meaning if you don't define it, the browser will connect to it by default

     

    Then nginx will connect to your container on its internal port and will proxy the connection

     

    You may need to read up on how reverse proxy works to learn the basics of the concept. Google is your friend. 

    Ok I get now how it roughly works, however I'm still baffled as to why it isn't loading correct for me. It just "refused to connect". proxy_pass url is definitely correct. I even typed in the exact server_name ombi.domain.com. If anyone has any ideas on how to solve it I would appreciate it a lot! 

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    2 minutes ago, aptalca said:

    Letsencrypt is listening on port 443, the default port for https

    Sorry but I don't understand, ah so you mean so we can't ever do something like https://ombi.domain.com:12345 because https overwrites the 12345 port with 443? If so that is ok for me, since I want https://ombi.domain.com to point to http://192.168.1.55:12345. The problem now is I'm getting ERR_CONNECTION_REFUSED when accessing https://ombi.domain.com.

     

    I manage to solve Point 1 by adding this server block of code in case someone is looking for it too:

      

    server {
	listen 80 default_server;
	server_name _;
	return 301 https://$host$request_uri;
}

     

     

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted · Edited by CyberMew

    23 minutes ago, aptalca said:

    Just run letsencrypt on unraid, put in your domain and subdomains, make sure to set "only_subdomains" to true so it doesn't try to validate your main domain with unraid and it will be set up. Then you can do the reverse proxies for transmission and such

    I got it working lets encrypt part now, but however the server part doesnt seems to be working..

     

    Currently ombi.domain.com is pointing to my server's wan ip address. I have portforwarding done for 12345.

     

    If I access http://ombi.domain.com:12345, it loads correctly. However if I do https://ombi.domain.com:12345, it redirects me back to http.

     

    I actually wanted it to:

    1. when accessing http, redirect to https

    2. when access subdomain, it loads ombi, no manual input of port required.

     

    This is my current default file: 

    server {
	listen 443 ssl;

	root /config/www;
	index index.html index.htm index.php;

	server_name ombi.*;

# removed the default ssl stuff here for brevity

	client_max_body_size 0;

	location / {
		include /config/nginx/proxy.conf;
		proxy_pass http://192.168.1.55:12345;	
	}
}

    Not sure if I am doing this correctly?

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted · Edited by CyberMew

    I have a main domain that is under hosting by dreamhost and bought/handled by namecheap. My www.domain.com is already https by lets encrypt under dreamhost hosting. What should I do in order to get mysubdomains.domain working under our lets encrypt, no matter the ports? Currently I have ddns to sub1.domain.com pointing to namecheap name servers and namecheap is pointing the subdomain to my unraid machine via A + Dynamic DNS Record. Hence something like sub1.domain.com:9091 is pointing to my transmission docker without issues. However I want it to be directed/protected by https, and same if I want sub2.domain.com (CNAME to sub1.domain.com). Do I need to have hosting for those subdomains or something? Do I have to turn off SSL for my domain in dreamhost for it to work?

×
×
  • Create New...