Highlighted
Absent Member.
Absent Member.
1226 views

Appliance 2 - certificate issues

Hi All,

Originally running iPrint Appliance 1, but discovered that our server certificates had expired after receiving the errors:

Authorization Required.
Ipp Error: 0xF0191
Http Error: 401

Followed TID 7016720 but it did not solve the problem, we rec'd a different error, however did not proceed any further as we were planning on migrating to the updated appliance.

After the migration, printing services were fine, but once again iManager returned the same error when trying to configure/manage a printer.

We checked the server certificates and found that they were valid. We eventually decided to renew the certificates again as per TID 7016720, but it made no difference.

In additional to the original error, the appliance is also behaving the same as described in TID 7017887, RPC / 500 error at the appliance management screen. We weren't able to obtain the field test file (novell-iprint-mobile-2.0.0_FTF_985902-26.1.x86_64.rpm) as mentioned in the TID.

While searching for the file we came across TID 7017912 which referenced the same script as mentioned in TID 7017887, so we decided to download and run the script, but again no change.

What we have noticed is when accessing the appliance via https://IPAddress:9443 our 3rd party SSL certificate is recognised by the browse. After we login we receive the RPC / 500 errors, but the 3rd party SSL is still being used. When we switch to iManager, the local server certificate is present to the browser and fails as not secure.

Is this correct?

Or do we need to configure iManager with the 3rd party SSL certificate?

Any advice on what to do next is greatly appreciated. We are considering requesting a new SSL certificate.

Regards
Alan
0 Likes
4 Replies
Highlighted
Visitor.

Re: Appliance 2 - certificate issues

Alan,

I had problems with a 1.x applicance too, and in the end, I setup a
brand new 2.1 appliance, copied the driver store from the 1.x to the
new 2.x, then recreated all the printers on the 2.1 appliance.

I had both the expired certificates, but I also noticed that one of the
1.x patches caused the print manager to use the iPrint server's CNAME
instead of its A record, and that caused lots of problems (could not
manage printers).

Unless your setup is really complex, recreating the appliance from
scratch may be the path of least problems.

Jeff

On 2016-08-30 04:47:02 +0000, Alan Lew said:

> Hi All,
>  
> Originally running iPrint Appliance 1, but discovered that our server
> certificates had expired after receiving the errors:
>  
> Authorization Required.
> Ipp Error: 0xF0191
> Http Error: 401
>  
> Followed TID 7016720 but it did not solve the problem, we rec'd a
> different error, however did not proceed any further as we were
> planning on migrating to the updated appliance.
>  
> After the migration, printing services were fine, but once again
> iManager returned the same error when trying to configure/manage a
> printer.
>
> We checked the server certificates and found that they were valid. We
> eventually decided to renew the certificates again as per TID 7016720,
> but it made no difference.
>  
> In additional to the original error, the appliance is also behaving the
> same as described in TID 7017887, RPC / 500 error at the appliance
> management screen. We weren't able to obtain the field test file
> (novell-iprint-mobile-2.0.0_FTF_985902-26.1.x86_64.rpm) as mentioned in
> the TID.
>  
> While searching for the file we came across TID 7017912 which
> referenced the same script as mentioned in TID 7017887, so we decided
> to download and run the script, but again no change.
>
> What we have noticed is when accessing the appliance via
> https://IPAddress:9443 our 3rd party SSL certificate is recognised by
> the browse. After we login we receive the RPC / 500 errors, but the 3rd
> party SSL is still being used. When we switch to iManager, the local
> server certificate is present to the browser and fails as not secure.
>  
> Is this correct?
>  
> Or do we need to configure iManager with the 3rd party SSL certificate?
>  
> Any advice on what to do next is greatly appreciated. We are
> considering requesting a new SSL certificate.
>  
> Regards
> Alan


0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Appliance 2 - certificate issues

Thanks Jeff,

Looks like that is what we'll be doing.
BTW, what's different between appliance 2 and 2.1, the download states it's an evaluation?

cheers
Alan

regards
Alan


>>> jeff<jsessler@no-mx.forums.microfocus.com> 31/8/2016 4:44 AM >>>


Alan,

I had problems with a 1.x applicance too, and in the end, I setup a brand new 2.1 appliance, copied the driver store from the 1.x to the new 2.x, then recreated all the printers on the 2.1 appliance.

I had both the expired certificates, but I also noticed that one of the 1.x patches caused the print manager to use the iPrint server's CNAME instead of its A record, and that caused lots of problems (could not manage printers).

Unless your setup is really complex, recreating the appliance from scratch may be the path of least problems.

Jeff

On 2016-08-30 04:47:02 +0000, Alan Lew said:

Hi All,

Originally running iPrint Appliance 1, but discovered that our server certificates had expired after receiving the errors:

Authorization Required.
Ipp Error: 0xF0191
Http Error: 401

Followed TID 7016720 but it did not solve the problem, we rec'd a different error, however did not proceed any further as we were planning on migrating to the updated appliance.

After the migration, printing services were fine, but once again iManager returned the same error when trying to configure/manage a printer.

We checked the server certificates and found that they were valid. We eventually decided to renew the certificates again as per TID 7016720, but it made no difference.

In additional to the original error, the appliance is also behaving the same as described in TID 7017887, RPC / 500 error at the appliance management screen. We weren't able to obtain the field test file (novell-iprint-mobile-2.0.0_FTF_985902-26.1.x86_64.rpm) as mentioned in the TID.

While searching for the file we came across TID 7017912 which referenced the same script as mentioned in TID 7017887, so we decided to download and run the script, but again no change.

What we have noticed is when accessing the appliance via https://IPAddress:9443 our 3rd party SSL certificate is recognised by the browse. After we login we receive the RPC / 500 errors, but the 3rd party SSL is still being used. When we switch to iManager, the local server certificate is present to the browser and fails as not secure.

Is this correct?

Or do we need to configure iManager with the 3rd party SSL certificate?

Any advice on what to do next is greatly appreciated. We are considering requesting a new SSL certificate.

Regards
Alan
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Appliance 2 - certificate issues

Hi All,

Ok,the new iprint appliance 2.1 is set up. Is there a quick way of exporting just the associated iprint objects, eg. printers, driver profiles...etc. from the old 2.0 appliance to the new 2.1 appliance?

I know I could have migrated the 2.0 appliance into the 2.1 appliance, but did not want to risk the same problem with server certificates when we migrated from the 1.1 appliance to the 2.0 appliance.

Any advice is appreciated.

regards
Alan


>>> Alan Lew<LewA@law.anu.edu.au> 1/9/2016 3:43 PM >>>


Thanks Jeff,

Looks like that is what we'll be doing.
BTW, what's different between appliance 2 and 2.1, the download states it's an evaluation?

cheers
Alan

regards
Alan


>>> jeff<jsessler@no-mx.forums.microfocus.com> 31/8/2016 4:44 AM >>>


Alan,


I had problems with a 1.x applicance too, and in the end, I setup a brand new 2.1 appliance, copied the driver store from the 1.x to the new 2.x, then recreated all the printers on the 2.1 appliance.


I had both the expired certificates, but I also noticed that one of the 1.x patches caused the print manager to use the iPrint server's CNAME instead of its A record, and that caused lots of problems (could not manage printers).


Unless your setup is really complex, recreating the appliance from scratch may be the path of least problems.


Jeff


On 2016-08-30 04:47:02 +0000, Alan Lew said:


Hi All,

Originally running iPrint Appliance 1, but discovered that our server certificates had expired after receiving the errors:

Authorization Required.
Ipp Error: 0xF0191
Http Error: 401

Followed TID 7016720 but it did not solve the problem, we rec'd a different error, however did not proceed any further as we were planning on migrating to the updated appliance.

After the migration, printing services were fine, but once again iManager returned the same error when trying to configure/manage a printer.


We checked the server certificates and found that they were valid. We eventually decided to renew the certificates again as per TID 7016720, but it made no difference.

In additional to the original error, the appliance is also behaving the same as described in TID 7017887, RPC / 500 error at the appliance management screen. We weren't able to obtain the field test file (novell-iprint-mobile-2.0.0_FTF_985902-26.1.x86_64.rpm) as mentioned in the TID.

While searching for the file we came across TID 7017912 which referenced the same script as mentioned in TID 7017887, so we decided to download and run the script, but again no change.


What we have noticed is when accessing the appliance via https://IPAddress:9443 our 3rd party SSL certificate is recognised by the browse. After we login we receive the RPC / 500 errors, but the 3rd party SSL is still being used. When we switch to iManager, the local server certificate is present to the browser and fails as not secure.

Is this correct?

Or do we need to configure iManager with the 3rd party SSL certificate?

Any advice on what to do next is greatly appreciated. We are considering requesting a new SSL certificate.

Regards
Alan
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Appliance 2 - certificate issues

On 08/30/2016 06:47 AM, Alan Lew wrote:
> Hi All,
>
> Originally running iPrint Appliance 1, but discovered that our server
> certificates had expired after receiving the errors:
>
> Authorization Required.
> Ipp Error: 0xF0191
> Http Error: 401
>
> Followed TID 7016720 but it did not solve the problem, we rec'd a
> different error, however did not proceed any further as we were planning
> on migrating to the updated appliance.
>
> After the migration, printing services were fine, but once again
> iManager returned the same error when trying to configure/manage a printer.
>
> We checked the server certificates and found that they were valid. We
> eventually decided to renew the certificates again as per TID 7016720,
> but it made no difference.
>
> In additional to the original error, the appliance is also behaving the
> same as described in TID 7017887, RPC / 500 error at the appliance
> management screen. We weren't able to obtain the field test file
> (novell-iprint-mobile-2.0.0_FTF_985902-26.1.x86_64.rpm) as mentioned in
> the TID.
>
> While searching for the file we came across TID 7017912 which referenced
> the same script as mentioned in TID 7017887, so we decided to download
> and run the script, but again no change.
>
> What we have noticed is when accessing the appliance via
> https://IPAddress:9443 our 3rd party SSL certificate is recognised by
> the browse. After we login we receive the RPC / 500 errors, but the 3rd
> party SSL is still being used. When we switch to iManager, the local
> server certificate is present to the browser and fails as not secure.
>
> Is this correct?
>
> Or do we need to configure iManager with the 3rd party SSL certificate?
>
> Any advice on what to do next is greatly appreciated. We are considering
> requesting a new SSL certificate.
>
> Regards
> Alan



With appliance 2.x you can solve cert issues in less than a minute using
certman.sh

https://www.novell.com/documentation/iprint-appliance-2/iprint_admin/data/certificates.html#b1ijo48i

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.