<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Web Service Management &#8211; Hostry Help Center</title>
	<atom:link href="https://help.hostry.com/article-categories/web-service-management/feed/" rel="self" type="application/rss+xml" />
	<link>https://help.hostry.com</link>
	<description>Full information on how to use HOSTRY, provided by 24/7 community based support</description>
	<lastBuildDate>Thu, 03 Dec 2020 10:24:54 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=5.9.12</generator>

<image>
	<url>https://help.hostry.com/wp-content/uploads/cache/2021/01/cropped-apple-icon-180x180-1/836712163.png</url>
	<title>Web Service Management &#8211; Hostry Help Center</title>
	<link>https://help.hostry.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How To Protect NGINX web server from Logjam atack on CentOS</title>
		<link>https://help.hostry.com/knowledge-base/how-to-protect-nginx-web-server-from-logjam-atack-on-centos/</link>
					<comments>https://help.hostry.com/knowledge-base/how-to-protect-nginx-web-server-from-logjam-atack-on-centos/#comments</comments>
		
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Thu, 22 Aug 2019 11:01:21 +0000</pubDate>
				<guid isPermaLink="false">https://help.hostry.com/?post_type=ht_kb&#038;p=567</guid>

					<description><![CDATA[When using a security certificate, many are confident in 100% protection of their web server, but we want to tell that there is a vulnerability in the security certificate. It cannot be called an ordinary vulnerability; rather, it is a small hole in the protocol itself during depreciation of SSL3 [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>When using a security certificate, many are confident in 100% protection of their web server, but we want to tell that there is a vulnerability in the security certificate. It cannot be called an ordinary vulnerability; rather, it is a small hole in the protocol itself during depreciation of SSL3 and a phased transition to the use of SSL2.</p>



<p>Today there are many web services that are vulnerable to this Logiam attack. We will try to understand how it can be done to secure your server. We will be talking about servers with the operating system CentOS, version 6 and 7.</p>



<h2 id="specific-actions" >Specific actions </h2>



<p>First, check to see if your server is actually vulnerable by checking Qualys SSL. If your server is vulnerable, there will be a message at the top of the page. After you confirm that the server is vulnerable, enter the NGINX installation directory</p>



<pre class="wp-block-code"><code>cd /etc/nginx/
mkdir keygroup
cd keygroup</code></pre>



<p>Next, you need to run the following command to create a key group</p>



<pre class="wp-block-code"><code>openssl dhparam -out dhsecure.pem 2048</code></pre>



<p>The next step is to add a new key group to your NGINX configuration</p>



<pre class="wp-block-code"><code>cd /etc/nginx/
vi .conf</code></pre>



<p>Next, add<strong><code> ssl_dhparam ... </code></strong>a line of code that is visible below inside each SSL server block and then update all server blocks. Update all blocks of your SSL server accordingly</p>



<pre class="wp-block-code"><code>server {
listen 443 ssl;
...
location / {
...
ssl_dhparam /etc/nginx/keygroup/dhsecure.pem
...
}</code></pre>



<p>Then a reboot of the NGINX web server should follow</p>



<pre class="wp-block-code"><code>service nginx reload</code></pre>



<p>Finally, test the server again with SSL certificate verification</p>
]]></content:encoded>
					
					<wfw:commentRss>https://help.hostry.com/knowledge-base/how-to-protect-nginx-web-server-from-logjam-atack-on-centos/feed/</wfw:commentRss>
			<slash:comments>460</slash:comments>
		
		
			</item>
		<item>
		<title>KVM Virtualization: Features and Benefits</title>
		<link>https://help.hostry.com/knowledge-base/kvm-virtualization-features-and-benefits/</link>
					<comments>https://help.hostry.com/knowledge-base/kvm-virtualization-features-and-benefits/#comments</comments>
		
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Tue, 09 Jul 2019 07:31:41 +0000</pubDate>
				<guid isPermaLink="false">https://help.hostry.com/?post_type=ht_kb&#038;p=48</guid>

					<description><![CDATA[HOSTRY virtual servers have KVM virtualization. We will look at it in more detail in order to show its main features and advantages in using. Choosing our servers you can be sure that you get a part of the server machine completely in your management and administration and at a [&#8230;]]]></description>
										<content:encoded><![CDATA[
<figure class="wp-block-image is-resized"><img src="https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-09-09-57-48.png" alt="" class="wp-image-50" width="546" height="387" srcset="https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-09-09-57-48.png 346w, https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-09-09-57-48-300x213.png 300w, https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-09-09-57-48-50x36.png 50w, https://help.hostry.com/wp-content/uploads/2019/07/Screenshot-from-2019-07-09-09-57-48-320x228.png 320w" sizes="(max-width: 546px) 100vw, 546px" /></figure>



<p></p>



<p><a href="https://hostry.com/products/vps/">HOSTRY</a> virtual servers have <strong>KVM virtualization</strong>. We will look at it in more detail in order to show its main features and advantages in using. Choosing our servers you can be sure that you get a part of the server machine completely in your management and administration and at a very reasonable price!</p>



<h2 id="definition" >Definition</h2>



<p><strong>KVM </strong>is a virtualization technology that calls the user to create practically his own analogue of a dedicated server. Each service on this virtualization is completely separately isolated from the other and has its own operating system kernel.<br>From the outset, KVM supported only x86 processors. To date, a very extensive Spector processor and OS has been added. Today it is easy to use, unpretentious to resources and at the same time quite functional hypervisor. It allows you to deploy a virtualization platform in a short time, they state in <strong><a href="https://www.kaspersky.com/blog/kaspersky-security-for-virtualization-reasons-for-the-fourth-hypervisor-support/15135/">Kaspersky Lab.</a></strong></p>



<p></p>



<h2 id="features" >Features</h2>



<p>The main features of this virtualization are the following: </p>



<ul><li><strong>It is possible to work and connect any operating system: if the servers are serviced on Linux, you can connect any other OS (Windows, FreeBSD); </strong></li><li><strong>It is possible to format the full disk space for any file system; </strong></li><li><strong>This virtualization has the ability to modify the kernel of the operating system.</strong></li></ul>



<p></p>



<h2 id="further-implementations" >Further implementations</h2>



<p></p>



<p>KVM virtualization is improving. It needs support for virtual networks and file storage systems. There will also be work on improving reliability, power management, HPC / system support, and virtual processor scalability.</p>



<p></p>



<p>Order now<strong><span style="text-decoration: underline;"><em> Virtual Private Server</em></span></strong> at HOSTRY Company by clicking the link below:</p>



<p><a href="https://hostry.com/products/vps/"><strong>https://hostry.com/products/vps/</strong></a></p>



<p></p>



<p></p>
]]></content:encoded>
					
					<wfw:commentRss>https://help.hostry.com/knowledge-base/kvm-virtualization-features-and-benefits/feed/</wfw:commentRss>
			<slash:comments>466</slash:comments>
		
		
			</item>
		<item>
		<title>Monitoring Debian Server Status Using Munin</title>
		<link>https://help.hostry.com/knowledge-base/monitoring-debian-server-status-using-munin/</link>
					<comments>https://help.hostry.com/knowledge-base/monitoring-debian-server-status-using-munin/#comments</comments>
		
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Thu, 19 Mar 2020 11:26:19 +0000</pubDate>
				<guid isPermaLink="false">https://help.hostry.com/?post_type=ht_kb&#038;p=1534</guid>

					<description><![CDATA[Munin is an online resource monitoring tool that can help analyze resource trends and “what just led to a decrease in our productivity?” Problems. It is designed to be very plug and play. The default setting provides many graphs with virtually no work. Install The Necessary Packages Create a User [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p><strong><em><a href="http://munin-monitoring.org/">Munin </a></em></strong>is an online resource monitoring tool that can help analyze resource trends and “what just led to a decrease in our productivity?” Problems. It is designed to be very plug and play. The default setting provides many graphs with virtually no work. </p>



<h2 id="install-the-necessary-packages" >Install The Necessary Packages</h2>



<pre class="wp-block-code"><code>apt-get install munin munin-plugins-extra libwww-perl apache2-utils</code></pre>



<h2 id="create-a-user-to-access-the-web-interface" >Create a User To Access The Web Interface</h2>



<pre class="wp-block-code"><code>htpasswd -c /etc/munin/.htpasswd munin</code></pre>



<h2 id="enable-monitoring-plugins" > Enable Monitoring Plugins </h2>



<p>Next, you should choose the plugin that will be included, while creating a symbolic link for it</p>



<pre class="wp-block-code"><code>ln -s /usr/share/munin/plugins/cpu /etc/munin/plugins/cpu
ln -s /usr/share/munin/plugins/df /etc/munin/plugins/df
ln -s /usr/share/munin/plugins/forks /etc/munin/plugins/forks
ln -s /usr/share/munin/plugins/fw_packets /etc/munin/plugins/fw_packets
ln -s /usr/share/munin/plugins/ip_127.0.0.1 /etc/munin/plugins/ip_127.0.0.1
ln -s /usr/share/munin/plugins/load /etc/munin/plugins/load
ln -s /usr/share/munin/plugins/memory /etc/munin/plugins/memory
ln -s /usr/share/munin/plugins/processes /etc/munin/plugins/processes
ln -s /usr/share/munin/plugins/threads /etc/munin/plugins/threads
ln -s /usr/share/munin/plugins/uptime /etc/munin/plugins/uptime
ln -s /usr/share/munin/plugins/exim_mailqueue /etc/munin/plugins/exim_mailqueue
ln -s /usr/share/munin/plugins/exim_mailstats /etc/munin/plugins/exim_mailstats
ln -s /usr/share/munin/plugins/postfix_mailstats /etc/munin/plugins/postfix_mailstats
ln -s /usr/share/munin/plugins/postfix_mailqueue /etc/munin/plugins/postfix_mailqueue
ln -s /usr/share/munin/plugins/mysql_queries /etc/munin/plugins/mysql_queries
ln -s /usr/share/munin/plugins/nginx_request /etc/munin/plugins/nginx_request
ln -s /usr/share/munin/plugins/nginx_status /etc/munin/plugins/nginx_status
ln -s /usr/share/munin/plugins/apache_accesses /etc/munin/plugins/apache_accesses
ln -s /usr/share/munin/plugins/apache_processes /etc/munin/plugins/apache_processes</code></pre>



<h2 id="change-configuration" >Change Configuration</h2>



<p>First you need to edit the <strong>/etc/munin/munin.conf </strong>file for some basic settings. Then find and change <strong>[localhost.localdomain]</strong> your own hostname, for example <strong>your-server.example.com</strong>. Open and edit <strong>/etc/apache2/conf.d/munin</strong>.</p>



<p>Comment on the following lines: </p>



<pre class="wp-block-code"><code>Order allow,deny
Allow from localhost 127.0.0.0/8 ::1
Options None</code></pre>



<p>Then uncomment the following lines to enable authentication: </p>



<pre class="wp-block-code"><code># AuthUserFile /etc/munin/.htpasswd
# AuthName "Munin"
# AuthType Basic
# require valid-user</code></pre>



<p><strong><em>IMPORTANT!</em></strong> If your Apache web server is listening on a port that is different from 80, then you should definitely edit  <strong>/etc/munin/plugin-conf.d/munin-node</strong>. Add the following lines to the end of the file if your Apache is listening on port 8080:  </p>



<pre class="wp-block-code"><code>[apache_*]
env.ports 8080</code></pre>



<p>The final step will be to restart the services </p>



<pre class="wp-block-code"><code>/etc/init.d/munin-node restart
/etc/init.d/apache2 restart</code></pre>



<p>If all the steps are completed correctly, now you can access the munin web interface  <strong>http://YOUR_SERVER_IP/munin</strong> </p>



<h2 id="_" ></h2>



<p></p>
]]></content:encoded>
					
					<wfw:commentRss>https://help.hostry.com/knowledge-base/monitoring-debian-server-status-using-munin/feed/</wfw:commentRss>
			<slash:comments>457</slash:comments>
		
		
			</item>
	</channel>
</rss>
