Discuss

discuss@lists.centos.org

8 participants
34745 discussions

Step-by-Step Tutorial: How to Deploy cPanel Web Hosting Control Panel version 11.74 on CentOS 7.5 Linux Server version 1805 in Amazon AWS Cloud
by Turritopsis Dohrnii Teo En Ming 02 Sep '18

02 Sep '18

Step-by-Step Tutorial: How to Deploy cPanel Web Hosting Control Panel version 11.74 on CentOS 7.5 Linux Server version 1805 in Amazon AWS Cloud Secondary Subject/Topic: How to Setup a New Startup Web Hosting Company Using cPanel Web Hosting Control Panel version 11.74, CentOS 7.5 Linux Server version 1805, and Amazon AWS Cloud Tertiary Subject/Topic: How to Startup Your Own Internet Business Like China's Billionaire Jack Ma. Will Teo En Ming Be Able to Emulate Jack Ma? Objective: Experimental and Feasibility Studies for Teo En Ming's Startup Internet Business AUTHOR OF THIS TUTORIAL: MR. TURRITOPSIS DOHRNII TEO EN MING (ZHANG ENMING) @ TIME TRAVELLER ACADEMIC QUALIFICATIONS: (1) Bachelor of Engineering (Second Class Lower Honours) in Mechanical Engineering from National University of Singapore (Graduated DEC 2006), with Electives in Aerospace Engineering (2) Part Time Diploma (Conversion) in Computer Networking with 4 Distinctions from Singapore Polytechnic (Graduated 2017) (3) Full Time Diploma in Mechatronics Engineering with Merit from Singapore Polytechnic (Graduated 1998) (4) Certificate of Completion for CISCO Certified Network Associate (CCNA) 5-DAY Boot Camp from NTUC Learning Hub, Singapore, Year 2017 (5) National Infocomm Competency Framework (NICF) (Singapore) Certificate in Configuring a CISCO Router, Year 2017 (6) National Infocomm Competency Framework (NICF) (Singapore) Certificate in Configuring a CISCO Switch, Year 2017 (7) GCE "O" Levels with 7 A1s and 1 A2, Top Student Award, Graduated 1994 (8) Primary School Leaving Examination (PSLE) Score of 238, Graduated 1990 AGE: 40 YEARS OLD (as at 1ST SEPTEMBER 2018) COUNTRY OF RESIDENCE: REPUBLIC OF SINGAPORE DATE: 1ST SEPTEMBER 2018 SATURDAY TIME: 8:30 PM SINGAPORE TIME, GREENWICH MEAN TIME+8 PRIMARY EMAIL: teo.en.ming AT gmail.com SECONDARY EMAIL: teo.en.ming.BUSINESS AT gmail.com DOCUMENT VERSION: 1809.01 COPYRIGHT (C) 2018 TURRITOPSIS DOHRNII TEO EN MING. This step-by-step tutorial is written by Teo En Ming in Singapore. NB: This document consists of a total of 251 steps. SECTION 1: DEPLOYING THE CPANEL DNSONLY DOMAIN NAME SERVERS =========================================================== 001. Login to your Amazon AWS Cloud account. 002. Click Services > Compute > EC2 003. Click Network and Security > Elastic IPs 004. Click Allocate new address. Click Allocate. New address request succeeded, for example, 13.58.134.234. 005. Click Instances > Instances. Click Launch Instance. 006. Click AWS Marketplace. 007. Search for CentOS. 008. Select CentOS 7 (x86_64) - with Updates HVM Amazon Machine Image (AMI). Click Continue. 009. Select General Purpose, t2.micro, 1 vCPU, 1 GB RAM (FREE TIER ELIGIBLE). 010. Click Next: Configure Instance Details. 011. Select Network: <Your VPC network> 012. Select Subnet: <Your subnet> | Public subnet | us-east-2a 013. Click Protect against accidental termination. 014. Click Next: Add Storage 015. Click Next: Add Tags 016. Enter Key = Name and Value = CPANEL NAME SERVER 1 017. Click Next: Configure Security Group 018. Click Select an existing security group 019. Select NS_SG (Name Server Security Group). 020. Click Review and Launch. Click Launch. 021. Select a key pair. 022. Click Network and Security > Elastic IPs. 023. Select Elastic IP 13.58.134.234. 024. Click actions > associate address. 025. Select Instance: CPANEL NAME SERVER 1 026. Click Allow Elastic IP to be reassociated if already attached. 027. Click Associate. 028. Login to CentOS 7 Linux Server using Putty. Use centos as username. Follow the Installation Guide - cPanel DNSONLY Installation at https://documentation.cpanel.net/display/74Docs/Installation+Guide+-+cPanel… SECTION 2: INSTALLING CPANEL DNSONLY NAME SERVER 1 ================================================== 029. cd /home 030. sudo curl -o latest-dnsonly -L https://securedownloads.cpanel.net/latest-dnsonly 031. sudo sh latest-dnsonly 032. sudo /scripts/configure_firewall_for_cpanel 033. sudo passwd root 034. Go to https://13.58.134.234:2087 and login. 035. Click I Agree. Go to Step 2 036. Enter Server Contact Email Address. 037. Enter Server Hostname, for example, ns1.teo-en-ming-corp.com 038. Enter Primary Resolver, e.g. 8.8.8.8 039. Enter Secondary Resolver, e.g. 8.8.4.4 040. Click Save and Go to Step 3. 041. Click Skip this step and use my server's default settings. 042. Select BIND DNS Server. 043. Nameserver 1: ns1.teo-en-ming-corp.com 044. Nameserver 2: ns2.teo-en-ming-corp.com 045. Request another Elastic IP address in Amazon AWS Cloud as per steps above, e.g. 52.15.109.147 046. Click Configure Nameserver A Records 047. ns1.teo-en-ming-corp.com IPv4: 13.58.134.234 048. ns2.teo-en-ming-corp.com IPv4: 52.15.109.147 049. Click Finish. 050. Login to your domain registrar, e.g. godaddy.com 051. Select your domain name, e.g. teo-en-ming-corp.com 052. Click Manage DNS. Click Host names. Click Add. 053. Map ns1.teo-en-ming-corp.com to 13.58.134.234. Click Save. 054. Click Add. 055. Map ns2.teo-en-ming-corp.com to 52.15.109.147. Click Save. 056. Select your domain name, e.g. teo-en-ming-corp.com 057. Click Manage DNS. 058. Under Nameservers, click Change. Select Custom. 059. Under Nameserver, enter ns1.teo-en-ming-corp.com and ns2.teo-en-ming-corp.com 060. Log out from your domain registrar, e.g. godaddy.com 061. You should now be able to access https://ns1.teo-en-ming-corp.com:2087/ SECTION 3: INSTALLING CPANEL DNSONLY NAME SERVER 2 ================================================== 062. Go to Amazon AWS Management Console. 063. Click Instances > Instances. 064. Click Launch Instance. 065. Click AWS Marketplace. 066. Search for CentOS. 067. Select CentOS 7 (x86_64) - with Updates HVM Amazon Machine Image (AMI). Click Continue. 068. Select General Purpose, t2.micro, 1 vCPU, 1 GB RAM (FREE TIER ELIGIBLE). 069. Click Next: Configure Instance Details. 070. Select Network: <Your VPC network> 071. Select Subnet: <Your subnet> | Public subnet | us-east-2a 072. Click Protect against accidental termination. 073. Click Next: Add Storage. 074. Click Next: Add Tags. 075. Enter Key = Name and Value = CPANEL NAME SERVER 2 075. Click Next: Configure Security Group 076. Click Select an existing security group 077. Select NS_SG (Name Server Security Group). 078. Click Review and Launch. Click Launch. 079. Select a key pair. 080. Click Launch Instances. 081. Click Network and Security > Elastic IPs. 082. Select 52.15.109.147. 083. Click Actions > Associate address. 084. Select Instance: CPANEL NAME SERVER 2 085. Click Allow Elastic IP to be reassociated if already attached. 086. Click Associate. 087. Login to CentOS 7 Linux Server using Putty. Use centos as username. 088. cd /home 089. sudo curl -o latest-dnsonly -L https://securedownloads.cpanel.net/latest-dnsonly 090. sudo sh latest-dnsonly 091. sudo /scripts/configure_firewall_for_cpanel 092. sudo passwd root 093. Go to https://ns2.teo-en-ming-corp.com:2087 and login. 094. Click I Agree. Go to Step 2. 095. Enter Server Contact Email Address. 096. Enter Server Hostname: ns2.teo-en-ming-corp.com 097. Enter Primary Resolver, e.g. 8.8.8.8 098. Enter Secondary Resolver, e.g. 8.8.4.4 099. Click Save and Go to Step 3. 100. Click Skip this stemp and use my server's default settings. 101. Select BIND DNS Server. 102. Nameserver 1: ns1.teo-en-ming-corp.com 103. Nameserver 2: ns2.teo-en-ming-corp.com 104. Click Configure Nameserver A Records 105. ns1.teo-en-ming-corp.com IPv4: 13.58.134.234 106. ns2.teo-en-ming-corp.com IPv4: 52.15.109.147 107. Click Finish. SECTION 4: INSTALLING THE CPANEL WEB/VIRTUAL SERVER =================================================== Follow the Installation Guide at https://documentation.cpanel.net/display/74Docs/Installation+Guide 108. Click Network and Security > Elastic IPs 109. Click Allocate new address. Click Allocate. 110. New address request succeeded, e.g. 18.223.26.190 111. Click Instances > Instances. 112. Click Launch Instance. 113. Click AWS Martketplace. 114. Search for CentOS. 115. Select CentOS 7 (x86_64) - with Updates HVM Amazon Mage Image (AMI). Click Continue. 116. Select General purpose, t2.micro, 1 vCPU, 1 GB RAM (FREE TIER ELIGIBLE). 117. Click Next: Configure Instance Details. 118. Select Network: <Your VPC network> 119. Select Subnet: <Your subnet> | Public subnet | us-east-2a 120. Click Protect against accidental termination. 121. Click Next: Add Storage. 122. Change Size (GiB) from 8 to 30. It is still free tier eligible. 123. Click Next: Add Tags. 124. Enter Key = Name and Value = CPANEL WEB SERVER 125. Click Next: Configure Security Group 126. Click Select an existing security group. 127. Select VS_SG (Virtual Server Security Group). 128. Click Review and Launch. Click Launch. 129. Select a key pair. 130. Click Launch Instances. 131. Click Network and Security > Elastic IPs. 132. Select 18.223.26.190 133. Click Actions > Associate address. 134. Select Instance: CPANEL WEB SERVER. 135. Click Allow Elastic IP to be reassociated if already attached. 136. Click Associate. 137. Login to CentOS 7 Linux Server using Putty. Use centos as username. 138. sudo passwd root 139. su - root 140. cd /home && curl -o latest -L https://securedownloads.cpanel.net/latest && sh latest 141. /scripts/configure_firewall_for_cpanel 142. Go to https://18.223.26.190:2087 which is your Virtual Server and login. 143. Click I Agree. Go to Step 2. 144. Enter Server Contact Email Address. 145. Enter Server Hostname: cpanel.teo-en-ming-corp.com 146. Enter Primary Resolver, e.g. 8.8.8.8 147. Enter Secondary Resolver, e.g. 8.8.4.4 148. Click Save and Go to Step 3. 149. Click Skip this step and use my server's default settings. 150. Under Nameserver Configuration, select Disabled. DNS Server is not necessary for a Virtual Server. 151. Nameserver 1: ns1.teo-en-ming-corp.com 152. Nameserver 2: ns2.teo-en-ming-corp.com 153. Click Configure Nameserver A Records 154. ns1.teo-en-ming-corp.com IPv4: 13.58.134.234 155. ns2.teo-en-ming-corp.com IPv4: 52.15.109.147 156. Click Save and Go to Step 5. 157. Under FTP Configuration, select Pure-FTPD. 158. Click Enable Brute Force Protection. Select Everything. 159. Click Save and Go to Step 6. 160. Click Use filesystem quotas. 161. Click Finish. 162. Click Go to WHM. 163. Enable Global DCV Passthrough. 164. Enable The SSL/TLS Wizard in cPanel. 165. Click Save Settings. SECTION 5: CONFIGURING CPANEL DNS CLUSTER ========================================= SECTION 5.1: CONFIGURING DNS CLUSTER FOR THE PRIMARY NAME SERVER NS1.TEO-EN-MING-CORP.COM ========================================================================================= 166. Go to https://ns1.teo-en-ming-corp.com:2087 167. Click Clusters > DNS Cluster. 168. Click Enable DNS Clustering. 169. Click Return to Cluster Status. 170. Go to https://ns2.teo-en-ming-corp.com:2087 171. Click Clusters > DNS Cluster 172. Click Enable DNS Clustering. 173. Click Return to Cluster Status. For the following steps, please refer to Part 3: How I Built a cPanel Hosting Environment on Amazon AWS at https://blog.cpanel.com/part-3-how-i-built-a-cpanel-hosting-environment-on-… 174. Go to https://ns1.teo-en-ming-corp.com:2087 175. Click Development > Manage API Tokens. API = Application Programming Interface. 176. Click Generate Token. 177. Enter name: NS1 178. Click Everything 179. Click Save. 180. Copy your API token from Name Server 1 to the clipboard. 181. Go to https://18.223.26.190:2087 which is your Virtual Server. 182. Click Clusters > DNS Cluster 183. Click Enable DNS Clustering 184. Click Return to Cluster Status. 185. Select Backend Type: cPanel 186. Click Configure. 187. Remote cPanel & WHM DNS host: ns1.teo-en-ming-corp.com 188. Remote server username: root 189. Paste the API token from Name Server 1. 190. Click Setup Reverse Trust Relationship 191. Set DNS Role to Synchronize Changes. 192. Click Submit. 193. Click Return to Cluster Status 194. Go to https://18.223.26.190:2087 which is your Virtual Server. 195. Click Development > Manage API Tokens. 196. Click Generate Token. 197. Enter Name: VS 198. Click Everything. 199. Click Save. 200. Copy the API Token from the Virtual Server to the clipboard. 201. Go to https://ns1.teo-en-ming-corp.com:2087 202. Click Clusters > DNS Cluster 203. Click Configure. 204. Remote cPanel & WHM DNS host: cpanel.teo-en-ming-corp.com 205. Remote server username: root 206. Paste the API Token from the Virtual Server. 207. Click Setup Reverse Trust Relationship. 208. Set DNS Role to Standalone. 209. Click Submit. It says DNS Lookup Failed for cpanel.teo-en-ming-corp.com 210. Go to https://18.223.26.190:2087 which is your Virtual Server. 211. Click DNS Functions. Click Add an A Entry for Your Hostname. 212. Hostname: cpanel.teo-en-ming-corp.com 213. Server Main IP: 18.223.26.190 214. Click Add Entry. Added cpanel.teo-en-ming-corp.com ok You should now be able to ping cpanel.teo-en-ming-corp.com 215. Go to https://ns1.teo-en-ming-corp.com:2087 216. Click Clusters > DNS Cluster 217. Click Configure. 218. Remote cPanel & WHM DNS host: cpanel.teo-en-ming-corp.com 219. Remote server username: root 220. Copy the API Token from the Virtual Server. 221. Click Setup Reverse Trust Relationship. 222. Set DNS Role to Standalone. 223. Click Submit. 224. Click Return to Cluster Status. SECTION 5.2: CONFIGURING DNS CLUSTER FOR THE SECONDARY NAME SERVER NS2.TEO-EN-MING-CORP.COM =========================================================================================== 225. Go to https://ns2.teo-en-ming-corp.com:2087 226. Click Development > Manage API Tokens 227. Click Generate Token 228. Enter Name: NS2 229. Click Everything 230. Click Save. 231. Copy the API Token from Name Server 2 to the clipboard. 232. Go to https://18.223.26.190:2087 which is your Virtual Server. 233. Click Clusters > DNS Cluster 234. Click Configure. 235. Remote cPanel & WHM DNS host: ns2.teo-en-ming-corp.com 236. Remote server username: root 237. Paste the API Token from Name Server 2. 238. Click Setup Reverse Trust Relationship. 239. Set DNS Role to Synchronize Changes. 240. Click Submit. 241. Go to https://ns2.teo-en-ming-corp.com:2087 242. Click Clusters > DNS Cluster 243. Click Configure. 244. Remote cPanel & WHM DNS host: cpanel.teo-en-ming-corp.com 245. Remote server username: root 246. Paste the API Token from the Virtual Server. 247. Click Setup Reverse Trust Relationship 248. Set DNS Role to Standalone. 249. Click Submit 250. Click Return to Cluster Status SECTION 6: CONCLUSION ===================== 251. You should now be able to access your Virtual Server at https://cpanel.teo-en-ming-corp.com:2087/ ===END OF TUTORIAL=== If you happen to find any mistake with my step by step tutorial, please drop me a message. ===BEGIN SIGNATURE=== Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017 [1] https://tdtemcerts.wordpress.com/ <https://tdtemcerts.wordpress.com/>[2] http://tdtemcerts.blogspot.sg/ <http://tdtemcerts.blogspot.sg/>[3] https://www.scribd.com/user/270125049/Teo-En-Ming <https://www.scribd.com/user/270125049/Teo-En-Ming>===END SIGNATURE===

5 5

kvm & keypad on Centos 7.5
by Gregory P. Ennis 02 Sep '18

02 Sep '18

Everyone, I have a lab computer I am using to test kvm. It was difficult to install with NetworkManager running. After I turned nm off I got the bridge to work and to stay in place. NetworkManager kept chaning things. I have several things I would like to learn and to tweak with KVM and virtal machines. The first small tweak is how to turn on the keypad on a keyboard. I have tried two logitech keyboards and both fail to allow the use of the keypad on the guest. On the host it works fine. I have a nvidia card in place with kmod-nvidia installed; the numeric keypad failed before and after kmod-nvidia was installed. Any ideas, or this a bug??? Greg Ennis

1 1

GNOME, numeric keypad & commas
by Nicolas Kovacs 02 Sep '18

02 Sep '18

Hi, Our local school has a 100 % CentOS network on servers and desktops. Until recently, we were using a highly customized Xfce desktop environment. Last week I decided to migrate all desktops from Xfce to GNOME, which went quite well. Now I have to sand down some rough edges. The secretary complained that she can't use the numeric keypad as before. She's using LibreOffice Calc a lot, and she has to type in a lot of numbers with commas. With Xfce this was not a problem. Under GNOME, this won't work anymore. As far as I can tell, this has to do with the locale-specific syntax of 0.00 vs 0,00. Our systems are all localized in french. Any idea how this can be solved? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

2 2

Certificates
by Chuck Campbell 02 Sep '18

02 Sep '18

I am getting myself confused, and need someone who fully understands this process to help me out a bot. I would like to obtain an ssl certificate, so I can run my own imap server on a machine in my office. My domain is hosted by networksolutions, but I don't run my imap server there. I am assuming I'll need to pay a CA to generate what I need, but I'm confused about what I need. I am running dovecot at teh moment, but my clients (iphone, windows laptops) say my ssl connection is not trusted. The phone just won't connect. I tried emailing the dovecot.pem file to my phone and installing it, but it just says it is not trusted. This leads me to obtaining a real CA issued certificate. I'm not sure what to do with it, once I get one, and then if I need to subsequently regenerate my dovecot.pem file?? Thanks, -chuck --

17 25

vdo statustics on Dedup?
by david 31 Aug '18

31 Aug '18

Folks I've started to use "vdo" instead of zfs in Centos 7. I hope this is a wise decision. However, I'm a bit mystified in decoding the "vdostats" output. I'd like to figure out how well deduplication is working. One measure would be to find two numbers: L = How many bocks are in use as reported to tools like df P = How many actual blocks are in use. Then a value such as L/P, which can never be less than 1, would be interesting. If I have typically four copies of everything, I'd expect to see L/P close to 4.00. What two numbers, in the "vdostats" do this if any? David

1 0

bash completion in C7
by wwp 31 Aug '18

31 Aug '18

Hello there, while bash completion was working great to me in CentOS6, since I'm using C7 I spend my day stuck on completion not working the way it should. The bad situations I'm facing are: - it doesn't expand *foo whereas there are *foo-named files in current dir, for instance: # rm *foo will show nothing whereas there's a file barfoo in curdir. - completion takes 10 sec to propose me something, I don't have an example right here but I'd prefer no completion instead of a completion that hangs for more than 3 sec. I don't care much about command-specific completion (command --switches and so on), but it generally fails in listing files in curdir, that is a huge fail to me. I have this installed: bash-4.2.46-30.el7.x86_64 bash-completion-2.1-6.el7.noarch bash-completion-extras-2.1-11.el7.noarch Didn't touch global or user prefs around bash completion if there are. Am I missing something or is it just an itchy fail, real pain in the *ss? Regards, -- wwp

3 8

TUTORIAL: How to Install Apache Web Server in CentOS 7.5 (1805) Linux in Amazon AWS Cloud with URL/HTTP/HTTPS Redirection
by Turritopsis Dohrnii Teo En Ming 31 Aug '18

31 Aug '18

TUTORIAL: How to Install Apache Web Server in CentOS 7.5 (1805) Linux in Amazon AWS Cloud with URL/HTTP/HTTPS Redirection AUTHOR OF THIS TUTORIAL: MR. TURRITOPSIS DOHRNII TEO EN MING (ZHANG ENMING) @ TIME TRAVELLER AGE: 40 YEARS OLD COUNTRY OF RESIDENCE: SINGAPORE DATE: 30TH AUGUST 2018 THURSDAY TIME: 10:49 AM SINGAPORE TIME Greenwich Mean Time+8 1. Sign up for Amazon AWS Cloud or Google Cloud Platform or Microsoft Azure Cloud or Ali Baba Cloud account (your preference). 2. Login to Amazon AWS Management Console. 3. Click EC2 under Compute. 4. Click Elastic IPs under Network and Security. 5. Click Allocate New Address. 6. Click the Allocate button. 7. You will receive a permanent public IPv4 address from Amazon AWS Cloud, eg. 18.223.148.223. Alternative IPv4 address: 18.220.9.93. IPv6 address is not applicable. 8. Click Instances under INSTANCES. 9. Click Launch Instance. 10. Click AWS Marketplace. 11. Search for CentOS in the Search box. Press ENTER. 12. Select CentOS 7 (x86_64) - with Updates HVM 1805_1 Amazon Machine Image (AMI). 13. Click Continue. 14. Select General purpose, t2.micro, 1 vCPU, 1 GB RAM (FREE TIER ELIGIBLE). 15. Click Next: Configure Instance Details. 16. Select Network: <Your VPC network>. 17. Select Subnet: <Your subnet> | Public subnet | us-east-2a. 18. Click Protect against accidental termination. 19. Click Next: Add Storage. 20. Click Next: Add Tags. 21. Click Next: Configure Security Group. 22. Click Select an existing security group. 23. Select VS_SG (Virtual Server Security Group). 24. Click Review and Launch. 25. Click Launch. 26. Select a Secure Shell (SSH) key pair. 27. Click Launch Instances. 28. Click Elastic IPs under Network and Security. 29. Select the Elastic IP 18.223.148.223. 30. Click Actions. 31. Click Associate address. 32. Select the Instance you have created previously. 33. Click Allow Elastic IP to be reassociated if already attached. 34. Click Associate. 35. Open Putty/SSH client and login to CentOS 7.5 (1805). 36. Login as username centos. 37. Sign Out from Amazon AWS Management Console. 38. Install Apache web server with the Secure Sockets Layer (SSL) module: sudo yum install httpd mod_ssl 39. Start the Apache web server process: sudo /usr/sbin/apachectl start 40. Visit and test your web server at 18.223.148.223 Using Google Chrome. 41. You should see an Apache Web Server test page. 42. Install the nano text editor in Linux: sudo yum install nano 43. Go to the main Apache web server configuration directory: cd /etc/httpd/conf 44. Edit the main Apache web server configuration file: sudo nano httpd.conf 45. Append the following code to the end of httpd.conf: <VirtualHost *:80> ServerName blogger.teo-en-ming.com Redirect / https://tdtemcerts.blogspot.sg </VirtualHost> Alternative Code: <VirtualHost *:80> ServerName wordpress.teo-en-ming.com Redirect / https://tdtemcerts.wordpress.com </VirtualHost> 46. Restart the Apache web server process: sudo /usr/sbin/apachectl restart 47. Open an Internet Protocol Security (IPsec) Virtual Private Networking (VPN) connection to your corporate network using Shrew Soft VPN client. 48. Open a Remote Desktop Connection to your Windows Server 2019 Active Directory Domain Controller. 49. Under Server Manager, click Tools. Then Click DNS (Domain Name Service). 50. Click Forward Lookup Zones. 51. Click TEO-EN-MING.COM 52. Right Click, select New Host (A or AAAA). 53. Fill in Hostname: blogger 54. Fill in IP address: 18.223.148.223 55. Click Add Host. 56. Alternative DNS Host Record: Fully Qualified Domain Name (FQDN): WORDPRESS.TEO-EN-MING.COM IP address: 18.220.9.93 57. Test http://blogger.teo-en-ming.com. It should redirect to https://tdtemcerts.blogspot.sg 58. Alternative test: http://wordpress.teo-en-ming.com. It should redirect to https://tdtemcerts.wordpress.com 59. Go to Apache web server alternative configuration directory: cd /etc/httpd/conf.d 60. Edit the Apache web server Secure Socket Layer (SSL) configuration file: sudo nano ssl.conf 61. Find the section that says <VirtualHost _default_:443> 62. Insert the following code: ServerName blogger.teo-en-ming.com Redirect / https://tdtemcerts.blogspot.sg Alternative Code: ServerName wordpress.teo-en-ming.com Redirect / https://tdtemcerts.wordpress.com 63. Restart the Apache web server process: sudo /usr/sbin/apachectl restart 64. Test https://blogger.teo-en-ming.com. It should redirect to https://tdtemcerts.blogspot.sg 65. Alternative test: https://wordpress.teo-en-ming.com. It should redirect to https://tdtemcerts.wordpress.com 66. USEFUL REFERENCES: (A) Article: Install Apache and PHP on CentOS 6 Link/URL: https://support.rackspace.com/how-to/centos-6-apache-and-php-install/ (B) Article: How To Create Temporary and Permanent Redirects with Apache and Nginx Link/URL: https://www.digitalocean.com/community/tutorials/how-to-create-temporary-an… 67. Exit Putty/SSH client. 68. END OF TUTORIAL. ===BEGIN SIGNATURE=== Turritopsis Dohrnii Teo En Ming's Academic Qualifications as at 30 Oct 2017 [1] https://tdtemcerts.wordpress.com/ [2] http://tdtemcerts.blogspot.sg/ [3] https://www.scribd.com/user/270125049/Teo-En-Ming ===END SIGNATURE===

3 2

Re: [CentOS] Mail has quit working
by Richard 30 Aug '18

30 Aug '18

> Date: Monday, August 27, 2018 09:57:01 -0400 > From: TE Dukes <tdukes(a)palmettoshopper.com> > >> From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of >> centos--- via CentOS >> Sent: Monday, August 27, 2018 9:31 AM >> >> On 08/27/2018 09:05 AM, TE Dukes wrote: >> > >> > >> > Thanks again! I still think it's a mail issue. I can't get mail >> > using usermin either. >> > >> > Think I'm going to remove the TLS stuff from postfix main.cf >> > that I added yesterday and retry. >> >> If I missed this further up thread my apologies - is SELinux >> enabled and are there any relevant exceptions being logged? > > Pretty sure SELinux is turned off unless it got turned on without my > knowledge through an updtate/upgrade. > > I removed the TLS lines from main.cf I added last night and > remotely did a reboot from here at work. > > Mail is again working!! I am skeptical to mark this thread solved > as I thought it was solved back in July. > > I think, removing my ISP's DNS servers from resolve.conf was the > fix, could be removing IPV6 from etc/hosts. Might put it back in > just to see. > As I indicated earlier, removing those lines from your postfix config will have no impact on your ability to reach your roundcube instance. Unlike the windowz world, you mostly don't need to "reboot" a machine after making changes to a service (e.g., your postfix config change). An unnecessary reboot can bring in many issues so makes debugging a problem difficult. Instead, restart the service in question (often a reload is all that's needed, but a service restart generally doesn't hurt in a single/lower user environment). Unless you are VPN-ing (or equiv) my sense is that you are currently getting to your mail (roundcube) from outside your network. Earlier, when it wasn't working, my sense was that you were inside. If that's true you can't really tell if your issue has been resolved as you are coming at things from different network directions.

3 5

missing CESA-2018:2571 Important CentOS 6 bind Security Update
by Ulf Volmer 30 Aug '18

30 Aug '18

Hello, i'm running bind on an up to date CentOS 6.10 and missing the bind update from the announcement above. [root@fw ~]# yum list bind Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * epel: ftp.nluug.nl Installed Packages bind.x86_64 32:9.8.2-0.68.rc1.el6 @base is there is something wrong on my side? Or with the CentOS- repo? (My repo config is on https://cloud.u-v.de/index.php/s/ksNcosfmBrN57SQ ) best regards Ulf

3 3

SecureBoot : rolling out new shim pkgs for CentOS 7.5.1804 in CR repository - asking for testers/feedback
by Fabian Arrotin 30 Aug '18

30 Aug '18

When we consolidated all CentOS Distro builders in a new centralized setup, covering all arches (so basically x86_64, i386, ppc64le, ppc64, aarch64 and armhfp those days), we wanted also to add redundancy where it was possible to. The interesting "SecureBoot" corner case came on the table and we had to find a different way to build the following packages: - shim (both signed and unsigned) - grub2 - fwupdate - kernel The other reason why we considered rebuilding it is that the cert we were using has expired : curl --location --silent https://github.com/CentOS/sig-core-SecureBoot/raw/master/CentOS_7/kernel/SO… | openssl x509 -inform der -text -noout|grep -A2 Validity While technically it doesn't really matter for Secureboot itself, it was better to get a new key/cert rolled-in and use the new one for new builds. That's where it's interesting as because shim embeds the certs in the Machine Owner Key (MOK), and that each other component used in the boot chain is validated against that (so grub2 first, then kernel and kernel modules) that means that once deployed , the new shim would not be able to boot previous grub2/kernel. But there is a solution for that : instead of "embedding" only the new cert, we can have both the old one and new one, permitting us to still boot older kernels but also the new ones we'll build/push soon (built on the new build system), and that's what we used for that new shim package. That's where we'd like you (SecureBoot users) to give us feedback about that new shim pkg. It was already validated on some hardware nodes, passed some QA tests, but we'd prefer to have more feedback. Worth noting that such rebuild has also a patch that should fix an issue we had with shim not allowing to import key in MOK through mokutil (see https://bugs.centos.org/view.php?id=14050) How can you test ? If you're using UEFI with SecureBoot enabled , we have signed/pushed those pkgs to the CR repository (see https://wiki.centos.org/AdditionalResources/Repositories/CR) That repo is by default disabled, but following command would let you update shim : yum update shim --enablerepo=cr Then reboot and it should work like before, so validating the boot chain (while still using grub2/kernel packages signed with previous key) We'd appreciate feedback on this list, or #centos-devel on irc.freenode.net I'd like to thank Patrick Uiterwijk and Peter Jones for their help for the patch and validation for that shim -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss