Can't get Mailparse installed

General Interworx Control Panel Info General Inquries
,
1

Hopefully someone might have experienced this before and knows what to do.

I’m trying to install Blesta, which requires the PECL Mailparse php extension.

[root@hq ~]# pecl install mailparse
pecl/mailparse requires PHP extension “mbstring”
No valid packages found
install failed

So I install mbstring…which says it’s already installed (even after an httpd restart)

[root@hq ~]# yum install php-mbstring
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile

Any ideas?

2

Hi Staxed

Michael (Licencecart) is your man to ask, he’s all blesta, and I’m sure he’ll be dropping on forum as soon as he reads this.

In the meantime, you could try yum install php-pecl-mailparse php-mbstring

or I believe there is a work around using pear (pear install pecl/mailparse)

I hope this helps a little

Many thanks

John

3

[QUOTE=d2d4j;25940]Hi Staxed

Michael (Licencecart) is your man to ask, he’s all blesta, and I’m sure he’ll be dropping on forum as soon as he reads this.

In the meantime, you could try yum install php-pecl-mailparse php-mbstring

or I believe there is a work around using pear (pear install pecl/mailparse)

I hope this helps a little

Many thanks

John[/QUOTE]

Yeah, I’ve known Mike for good long while with Blesta, was going to ask him (though this isn’t directly related to Blesta) but figured I’d ask here while I wait for him to come around :).

pear actually worked to install it (at least it said it did), but now I’m getting a 500 error that didn’t appear before…hmm.

4

got it fixed, when mbstring and mailparse were added to php.ini automatically, they were put in the wrong order :D.

5

Only just spotted this, I helped a customer last night with this, to help others it’s just this:

32bit Installation


wget http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.rpm
rpm -ivh epel-release-6-8.noarch.rpm
yum install php-mbstring php-pecl-mailparse

64bit Installation


wget http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
rpm -ivh epel-release-6-8.noarch.rpm
yum install php-mbstring php-pecl-mailparse
6

Hi Michael

I thought later that it might work with staxed original code if you set the no dependency check perhaps -n, but am a little slow sorry

Glad you had the answer though

Many thanks

John

7

[QUOTE=d2d4j;25944]Hi Michael

I thought later that it might work with staxed original code if you set the no dependency check perhaps -n, but am a little slow sorry

Glad you had the answer though

Many thanks

John[/QUOTE]

Not sure probably haha, I save ways which help us and when we’ve got the knowledgebase they will be on the frontend for anyone who wishes help with InterWorx mate :smiley:

8

[QUOTE=Licensecart;25943]Only just spotted this, I helped a customer last night with this, to help others it’s just this:


wget http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
rpm -ivh epel-release-6-8.noarch.rpm
yum install php-mbstring php-pecl-mailparse

[/QUOTE]

Thanks :slight_smile: you should post the 32bit version as well (I was using 32bit so that wouldn’t have worked for me).

Though, in my case, I try to avoid extra repos if possible, so managed to get it working without one :slight_smile: (as mentioned, it just activated mailparse and mbstring in the wrong order which is why it didn’t work initially).

…now if only I can figure out a weird SSL issue I’m having, lol.

9

[QUOTE=Staxed;25946]Thanks :slight_smile: you should post the 32bit version as well (I was using 32bit so that wouldn’t have worked for me).

Though, in my case, I try to avoid extra repos if possible, so managed to get it working without one :slight_smile: (as mentioned, it just activated mailparse and mbstring in the wrong order which is why it didn’t work initially).

…now if only I can figure out a weird SSL issue I’m having, lol.[/QUOTE]

Updated, what’s wrong with your SSL?

10

sent you a PM over on Blesta, and put in a ticket to support :).

notice: fake domains :smiley:

I am getting a 500 error when trying to use HTTPS on my billing panel area. When checking the server logs, this is the result I see.

[Fri Aug 15 13:46:54 2014] [warn] RSA server certificate wildcard CommonName (CN) `*.hostname.com’ does NOT match server name!?

The server hostname is host.domainone.com and there is a wildcard certificate for this domain on all services.

I also have a wildcard certificate for *.bililngdomain.net installed on that siteworx account.

If you go to http://my.billingdomain.net/admin you will see that it works.

But if you go to https://my.billingdomain.net.admin you will see the 500 error. But if you click on the certificate information you will see that it is using the billingdomain.net and not hostname.com…so I’m not sure why I’m getting this ssl error in the log.

11

Hi guys

If you pm or post the domain with the SSL on, I’ll run a check if you want.

If you have installed it and not restarted apache, it can sometimes error

Hope that helps

Many thanks

John

12

[QUOTE=Staxed;25948]sent you a PM over on Blesta, and put in a ticket to support :).

notice: fake domains :smiley:

I am getting a 500 error when trying to use HTTPS on my billing panel area. When checking the server logs, this is the result I see.

[Fri Aug 15 13:46:54 2014] [warn] RSA server certificate wildcard CommonName (CN) `*.hostname.com’ does NOT match server name!?

The server hostname is host.domainone.com and there is a wildcard certificate for this domain on all services.

I also have a wildcard certificate for *.bililngdomain.net installed on that siteworx account.

If you go to http://my.billingdomain.net/admin you will see that it works.

But if you go to https://my.billingdomain.net.admin you will see the 500 error. But if you click on the certificate information you will see that it is using the billingdomain.net and not hostname.com…so I’m not sure why I’m getting this ssl error in the log.[/QUOTE]

Replied on the forum PM.

13

And the fix for it is here (incase anyone else has this issue with Blesta/Interworx in the future). Sad part is I’m the one that started that thread last time I setup blesta on Interworx and I just completely forgot about it…

14

[QUOTE=Staxed;25951]And the fix for it is here (incase anyone else has this issue with Blesta/Interworx in the future). Sad part is I’m the one that started that thread last time I setup blesta on Interworx and I just completely forgot about it…

Glad you fixed it mate. The .htaccess I Gave you is good for SPDY :wink:

15

never messed with implementing SPDY…maybe I’ll give it a shot :slight_smile:

16

Sent instructions in pm and pasting them here:


wget -N https://dl-ssl.google.com/dl/linux/direct/mod-spdy-beta_current_x86_64.rpm  <--- 64Bit
wget -N https://dl-ssl.google.com/dl/linux/direct/mod-spdy-beta_current_i386.rpm  <--- 32Bit
yum install at
rpm -U mod-spdy-*.rpm

You’ll need to do this for every .htaccess with ssl enabled:


RewriteEngine   On
RewriteCond     %{HTTPS}        off
RewriteCond     %{SERVER_PORT}  ^80$ [NC]
RewriteRule     (.*)    https://%{HTTP_HOST}%{REQUEST_URI}