You are viewing limited content. For full access, please sign in.

Question

Question

web admin console "not a valid server name"

Administration
Updated February 10, 2015
asked on December 9, 2014 • Show version history

I am trying to register a server in the Web Administration Console. It happens to be the same name as the site. Yet the console tells me it is "not a valid server name" what does this mean Laserfiche? Everything else can see the server name.

0 0

Answer

SELECTED ANSWER
replied on January 27, 2015

Answered ---

The machine name had "_" characters in the machine name. HTTP protocols are not friendly to the use of "_" in a URL. The machine name was changed to use hyphens "-".

 

Then I rebound SSL (443) to the certificate, retracing the workflow above.

 

When I tested the Web Admin console it connected with no issues, including windows authentication.

 

Here is web references to online documentation that is relative to this issue.

http://stackoverflow.com/questions/794243/internet-explorer-ignores-cookies-on-some-domains-cannot-read-or-set-cookies

http://www.ietf.org/rfc/rfc2396.txt

3 0

Replies

replied on December 9, 2014

If you type in the IP address manually, does it work?

0 0
View 14 previous replies
replied on December 9, 2014

Yes, but then I get a certificate error when drilling down in the menu to log into the repository. The certificate is a domain certificate issued to the machine FQDN and matches.

0 0
replied on December 9, 2014

If you uncheck SSL, does it work?

0 0
replied on December 9, 2014

No, I have limited the connection to 443. Enabled SSL in Laserfiche and Firewall. Certificate is bound in IIS.
 

0 0
replied on December 9, 2014

Are you using a local certificate or one issued from elsewhere.  Have you configured the LF server itself to use SSL?

0 0
replied on December 9, 2014 • Show version history

Domain issued certificate. Yes, it's configured as noted in the installation documentation. 

http://www.laserfiche.com/support/webhelp/Laserfiche/9.2/en-US/AdminGuide/LFAdmin.htm#Using_SSL_TLS.htm 

 

The certificate is matched to the trusted root and both the root and local certificate are installed.

0 0
replied on December 9, 2014

Do you have Web Access too?  Was the certificate originally set up for Web Access or for both Web Access and the LF server?

0 0
replied on December 9, 2014

Yes, and it connects and I can browse the folders/files. In this case all LF products are on the same machine / same certificate.

Connected to view a document and metadata:

 

 

 

0 0
replied on December 9, 2014

Open MMC. Under MMC > Certificates (Local Computer) > Trusted Root Certification Authorities > Certificates, what shows there?

0 0
replied on December 9, 2014

Plenty of certificates ... including the domain root which signed the local cert. (no useful screenshot) The cert is current and not expired. Are you looking for anything in particular or just that it exists?

0 0
replied on December 9, 2014

The one you are using for Web Access and LF.  If it is listed there.

1. Open a command prompt window and run the following command

makecert -pe -n "CN=v-sup-2k8r2-2.laserfiche.com" -ss my -sr LocalMachine -a sha1 -sky exchange -eku 1.3.6.1.5.5.7.3.1 -in "LF Test Authority" -is ROOT -ir LocalMachine -sp "Microsoft RSA SChannel Cryptographic Provider" -sy 12 myhost.cer

 

Note that “v-sup-2k8r2-2” should be replaced with your actual LF Server computer name and "LF Test Authority" should be replaced with the name of the certificate you want to use for the LF server.

 

2. Now back in MMC, go to MMC > Certificates (Local Computer) > Personal > Certificates > [the certificate you just made]

3. Open the certificate and look at the details

4. Copy the Thumbprint value into notepad and remove all spaces

5. Open a new command prompt window and go to C:\Windows\System32. Then run the following command

http add sslcert ipport=0.0.0.0:443 certhash=thumbprint_value_without_spaces appid={00112233-4455-6677-8899-AABBCCDDEEFF}

6. Now go into the registry to HKEY_LOCAL_MACHINE\SOFTWARE\Laserfiche\Engine\8.0\HttpServ

7. Create a new dword called SSLPORT and set the value to be 443 (decimal)

8. Restart the Laserfiche Server service

9. Open the LF Admin Console and register a new LF Server instance using v-sup-2k8r2-2.laserfiche.com (the fqdn of your actual computer name) and make sure to also check the "connect with ssl" option

1 0
replied on December 9, 2014

Based on your earlier screenshots you have items 6-8 already.  Just skip to 9 at that point and try again.

0 0
replied on December 9, 2014

I think this is already in place. What are we specifically looking for? I checked the Hash on the certificate and the netsh binding. They match. I don't mean to be dismissive, but I'm looking for the specific change that you feel is not taken care of. I have run through this workflow before. THANKS - I'll come back to this tomorrow. 

0 0
replied on December 10, 2014

Everything points to a misconfigured SSL certificate or a bad DNS entry.  Is dev_lf_lfs.state.al the FQDN of the machine?

If you "ping -a IP" where "IP" is the IP address for the computer. does it return the same name?

0 0
replied on December 10, 2014 • Show version history

Yes. These match.  And the certificate works in all other situations tested, example initial login to the Web Admin Console Application and overall use of Web Access. Both connected over https using windows authentication with that certificate.

0 0
replied on December 10, 2014

Then there may be other issues. Please contact you VAR so we can open a case.

0 0
replied on December 10, 2014

Will do. At least we documented all the right steps. Someone will benefit from this post. Thanks for your time and consideration. If I can remember I'll post the resolution/response.

1 0
replied on December 11, 2014

Here are some error events reported in Chrome Developer Console and the Windows Event viewer that are associated with this issue.


Chrome Developer Console:

  1. ExeptionType: "System.ArgumentException"
  2. Message: "Value does not fall within the expected range."
  3. StackTrace: " at WebAdmin.QuickRetrieval.RepositoryManipulate.RegisterServer(String serverName, Boolean useSSL)"

 

Windows Application Logs:

Value does not fall within the expected range. 12/11/2014 7:32:12 AM: User: <<my user was here>> URL: https://<<my_server_was_here>>/WebAdmin/lfs/Home.aspx Message: Value does not fall within the expected range. Stack trace: at WebAdmin.QuickRetrieval.RepositoryManipulate.RegisterServer(String serverName, Boolean useSSL)

Firefox Browser Console expands to show the error associated with "QuickRetrievalHandler.aspx"

"GET https://<<my_server_was here>>/WebAdmin/QuickRetrievalHandler.aspx"

There is no documentation on Google or Laserfiche Support for "QuickRetrievalHandler" or "QuickRetrieval".

Best I can infer this is code incorporated by Laserfiche in question that might be out of date.

Source in  ...\Program Files\Laserfiche\WebAdmin\js-src\nocomp\QuickRetrieval.js

Cites:

/*
jQuery Url Plugin
* Version 1.0
* 2009-03-22 19:30:05
* URL: http://ajaxcssblog.com/jquery/url-read-get-variables/
* Description: jQuery Url Plugin gives the ability to read GET parameters from the actual URL
* Author: Matthias Jäggli
* Copyright: Copyright (c) 2009 Matthias Jäggli under dual MIT/GPL license.
*/

When I get some time I will promote this to technical support.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...