If you're obtaining the subsequent error whereas aggregation the most recent unharness of ffmpeg-php-0.6.0 , this article will allow you to savvy to induce this fix.
/usr/src/ffmpeg-php-0.6.0/ffmpeg_frame.c: In function âzim_ffmpeg_frame_toGDImageâ:
/usr/src/ffmpeg-php-0.6.0/ffmpeg_frame.c:336: error: âPIX_FMT_RGBA32â undeclared (first use in this function)
/usr/src/ffmpeg-php-0.6.0/ffmpeg_frame.c:336: error: (Each undeclared identifier is reported only once
/usr/src/ffmpeg-php-0.6.0/ffmpeg_frame.c:336: error: for each function it appears in.)
/usr/src/ffmpeg-php-0.6.0/ffmpeg_frame.c: In function âzim_ffmpeg_frame_ffmpeg_frameâ:
/usr/src/ffmpeg-php-0.6.0/ffmpeg_frame.c:421: error: âPIX_FMT_RGBA32â undeclared (first use in this function)
make: *** [ffmpeg_frame.lo] Error 1
Under the ffmpeg-php-0.6.0 directory modify the file: ffmpeg_frame.c with nano or vi editor and replace every instance of PIX_FMT_RGBA32 with PIX_FMT_RGB32
# nano ffmpeg_frame.c
# Search for PIX_FMT_RGBA32 and replace it with PIX_FMT_RGB32
# Exit from the editor
Then run the following commands:
# cd /usr/local/src/ffmpeg-php-0.6.0
# cp -aP ffmpeg_frame.loT ffmpeg_frame.lo
# make clean
# make install
This should fix the errors given above. Finally add the ffmpeg.so extension in php.ini and check phpinfo for the server you should see ffmpeg listed.
We'll guide you thru putting in and configuring CSF - Config Server Firewall, a preferred different to APF. CSF comes with LFD and works with or while not cPanel.
CSF Install Guide and the way To
CSF - Config Server Firewall could be a stateful packet scrutiny firewall, login/intrusion detection and security application for UNIX operating system servers. What will that mean in English? straightforward - it is a program that may greatly improve your dedicated server or VPS's security.
It's a firewall - therefore it will block/restrict ports you do not wish open, and prevents somebody from exploitation any port they require if they did break in.
It has intrusion detection - therefore it'll scan the log files and monitor failing login tries, like FTP word shot and block the science.
Those area unit the two massive things i favor concerning CSF - and it's a pleasant interface for the non tekki person, on cPanel servers.
If you've got another firewall put in, like APF, CSF will assist you mechanically take away the present firewall and install theirs instead. detain mind it will not migrate over your configuration.
Installation is kind of straightforward:
Login because the root user to SSH and run the subsequent commands.
rm -fv csf.tgz
tar -xzf csf.tgz
If you'd wish to disable APF+BFD (which you may ought to do if you've got
them put in otherwise they'll conflict horribly):
That's it. you'll then tack csf and lfd in WHM, or edit the files
directly in /etc/csf/*
Don't forget to:
1. tack the TCP_IN, TCP_OUT, UDP_IN and UDP_OUT choices within the csf configuration to suite your server
2. Restart csf and lfd
3. Set TESTING to zero once you are pleased with the firewall
csf is preconfigured to figure on a cPanel server with all the quality cPanel
ports open. It conjointly auto-configures your SSH port if it's non-standard on
You should make sure that kernel work daemon (klogd) is enabled. Typically, VPS
servers have this disabled and you ought to check /etc/init.d/syslog and build
sure that any klogd lines aren't commented out. If you alter the file,
remember to restart syslog.
Now - login to your cPanel server's WHM as root and attend the lowest left menu. If already logged in then reload the page. In Plugins - you may see: ConfigServer Security&Firewall
The firewall is STOPPED by default - it's not running. we want to designed it, so take it out of check Mode.
Click on Firewall Configuration
ETH_DEVICE =: Set this to eth+
TCP_IN/TCP_OUT/UDP_IN/UDP_OUT = : These area unit the ports you would like to go away open for your server to work. If you alter the default SSH port confirm to feature it here. conjointly add the other services you would possibly have running like Shoutcast or game servers. By default most of the ports used ought to already be designed.
MONOLITHIC_KERNEL = : zero solely amendment this to one if your firewall won't begin - otherwise leave it because it.
LF_DSHIELD = 0: amendment this selection to 86400. this is often associate automatic updated list of acknowledged offensive IPs. sanctioning this can stop them from having the ability to attach to your server.
Spam Protection Alerts
If you would like to feature some spam protection, CSF will facilitate. Look within the configuraiton for the following:
LF_SCRIPT_ALERT = zero amendment this to one. this can send associate email aware of the supervisor once the limit designed below is reached among associate hour.
LF_SCRIPT_LIMIT = one hundred amendment this to 250. this can warn you once associatey scripts sends out 250 email messages in an hour.
Configuration Complete - nearly
Scroll right down to the lowest and click on on amendment to save lots of the settings. Then click Restart csf+lfd
You should see an enormous page of settle for and close to the lowest you ought to see:
csf: TESTING mode is enabled - remember to disable it within the configuration
Starting lfd:[ OK ]
Click on come back
Now check all of your services to create positive everything is functioning - SSH, FTP, http. once you are doing a couple of fast tests return into the Firewall Configuration page.
TESTING = one amendment this to zero and click on amendment at the lowest. Then Restart csf+lfd
That's it, the firewall is with success put in and running!!
Firewall Status: Running - you ought to see this on the most CSF page in WHM.
Removing csf and lfd is even a lot of simple:
Detailed guide explaining what virtual hosting is.
Virtual reseller hosting offers the looks of a company's own server however the technical aspects of area sharing. Through virtual hosting, a developer will secure area on a server and have shared access to the server's options. Hosting firms offer this service by maintaining massive|an outsized|an oversized} server and thereon large server they maintain variety of virtual internet hosts. The machine examines that "name" it's being known as by and so responds fittingly. Thus, guests to the location enter through the name of the developer and so cannot acknowledge that another company's server really, hosts the location.
Simply explicit by Crowder and Crowder (2000), virtual servers area unit "nothing over directories on a tough drive. The internetmaster will create all of the directories appear like it were a completely practical web server". With a virtual internet host, you may have your own identity, however you may not be needed to keep up the instrumentation.
Virtual hosting packages area unit the foremost common on the net and provide an expert and well-established hunt for personal and tiny business websites. Financially, the typical virtual hosting account runs between $15 and $30 per month. Ample area and information measure for little businesses, multiple email accounts, cgi-bin access, and a T3 affiliation area unit common account options. further fees area unit usually needed for additional advanced options together with information software system or SSL (secure server) practicality.
ClamAV is an popular open source anti-virus toolkit for *nix, and while many people don’t find much value in using antivirus software on Unix, it is very useful for email scanning. cPanel’s hosting implementation allows end users to run scans on their home folders, public FTP folders, mail, and public_html.
It’s really hard to install ClamAV on cPanel – if you’re too lazy to click a couple buttons. Simply go to WHM > Manage Plugins and enable the ClamAV Connector, and you’re good to go.
After this is done, you can go to WHM > Configure ClamAV Scanner and set scanning options for the entire server or specific users:
You should now see a Virus Scanner option in cPanel. If you don’t, you may need to enable it in Feature Manager.
From here, cPanel users can run scans on any permitted items.
For administrators, here are a few quick commands that may be useful:
Update antivirus database:
Scan a directory and print out infected files:
clamav -ri /home
Scan a directly and remove infected files and emails:
clamav -ri –remove /home
One of the most common problems that hosting providers face is the issue of user email not being delivered to other mail servers. Not only does it annoy the end user, but it’s extremely frustrating for the server administrator to deal with since there’s not always a clear indication of why email doesn’t get delivered successfully. In this post I’ll explain a few tips for helping improve the reliability of your mail server, and some tips you can give to your end users that send mailing lists.’
Note: You can’t control the incoming email policies of remote mail servers or RBL’s. However, most email providers will not intentionally inconvenience their own users by blocking legitimate email, so if you continue to have problems, I’d recommend contacting the email administrator of the remote server.
1. Do you look like a spammer?
First of all, if you’re sending out massive mailing lists, whether you consider it spam or not, you’re asking for it. Out of a list of 100,000 people, you can expect that a couple hundred of them are going to prompt spam complaints to your email provider, especially of the emails are of a “spammy” nature. If you’re not sure where you sit on the line between spam and email marketing, take a look at this post.
2. Practice proper mailing list etiquette
As a mailing list grows, you’re occasionally going to have email addresses that become invalid, or users that no longer want to receive your email. Don’t think that by hiding your opt-out link, you’re going to keep a subscriber. The recipient is more likely to mark your email as spam than hunt around for a way to remove their email address from your list, so make things easier by putting your opt-out link at the top with a reminder of why you are sending the email. For example:
You are receiving this newsletter because you purchased a product on mywebsite.com and requested to receive notifications. If you no longer want to be part of this mailing list, please click <here>
That being said, it’s extremely important that you promptly honor opt-out requests, and regularly check for bounced email for addresses that may no longer exist.
In addition to this, when sending email locally, your SMTP hostname should simply be “localhost”.
3. Limit outgoing email
If you’re a hosting provider and aren’t specifically catering to users that do bulk mailing, you may want to limit how much email each users can send, and advise users with large mailing lists to use services like Constant Contact. Tweaking a mail server to effectively send huge amounts of email without issue can be very difficult, and isn’t something I’d recommend even offering for shared hosting platforms. In a shared environment where the actions of one user can affect many, outgoing email should be limited and then allowed on a per-case basis. There are two simple ways to do this:
- In WHM > Tweak Settings, set the outgoing mail limit . You can specifically allow domains to send more by adding them to /var/cpanel/maxemails on versions 11.26 and lower, or adding a MAX_EMAIL_PER_HOUR option to /var/cpanel/users/$user for cpanel 11.28 and higher.
- In exim.conf, set the following options:
recipients_max_reject = true
recipients_max = 50
The best way to do this so the change is retained over cPanel and Exim updates is to add the options in /etc/exim.conf.local under @CONFIG@, then run /scripts/buildeximconf
Exim considers each email as one email, regardless of how many recipients are in it. This may be an inconvenience to some users, but in reality any mailing list should be sent as one recipient per email. For larger organizations that use mailing lists for discussion, a listserv software like Mailman is a better solution.
4. Tighten up your mail server
If you’ve ever wanted to be the target of a spam hack, allowing PHP nobody mail is the best way to accomplish this. Hopefully by now you’re running suPHP, but if you’re still running PHP as a DSO, whenever a PHP script uses the mail() function to send email it’s going to do so as the user “nobody”, or whatever user that Apache runs as. Since the user “nobody” is a system user, it bypasses mailing limitations that you may have already set up via cPanel or exim.conf. This means that a rogue mailing script on your server can send out unlimited amounts of email and cause your server to get blacklisted. You can adjust this setting in WHM > Tweak Settings.
You’ll also want to make sure that SMTP Tweak is turned on:
It’s also a good idea to require sender verification, which can be enabled in WHM > Exim Configuration Editor
5. Always use SMTP
Similarly, mailing list software should be configured to use SMTP with a valid email address, username, and password. Don’t rely on sendmail or the php/perl mail functions – you need to send as a valid authenticated user. Most mailing list software supports the use of SMTP, and using PHP or perl it’s very easy to incorporate SMTP authentication.
6. Use DomainKeys and SPF records
You want other mail servers to know that when they get mail from you, it’s actually from your server and not spoofed. Consider using DKIM and SPF records to allow remote mail servers to authenticate your email. You’ll find that this may instantly improve your email delivery to services like Yahoo, MSN, and Hotmail.
7. Subscribe to Feedback loops
It’s very important for email administrators and hosting provides to subscribe to feedback loops. Many remote mail and blacklist providers offer them, and they can be a very useful tool for identifying possible spammers on your network, as well as preemptively resolving issues with mailing lists. If you don’t have an Abuse contact set up your domain and IP addresses, you should do that now – and register your IP(s). AOL, Hotmail, Yahoo, and Spamcop are excellent ones to be on. It’s also important to have your email@example.com address set up so people can contact you if they want to report spam from your server or network.
8. Monitor your IPs
As easy as it is to get blacklisted on the various RBL’s out there, you’ll want to be checking if your IPs may be listed and therefore causing your email to bounce. RBLmon.com is a good way to get started, or you can implement blacklist checking into your existing monitoring solution. The goal is to know when your IPs are blacklisted as soon as possible.
9. Use different IPs for email
By default, when you send email your email will go out on the main IP of the server. For sites that send large amounts of email, consider putting them on separate IPs so that they don’t affect the mail delivery of other users on the server, or the network in general.
10. Set up your DNS properly
It should go without saying that whatever IP you use to send mail should have a proper reverse DNS record, and the forward DNS of that PTR should match. For example, if your mail server is named mail.mydomain.com and points to 18.104.22.168, then the PTR for 22.214.171.124 should also be mail.mydomain.com. Ideally these records should match the EHLO/HELO name given by your MTA (Exim). This name can be altered in /etc/mailhelo if you have this option checked in WHM > Exim Configuration Editor.