Frontpage & private_html

J

jw00dy

Verified User
Joined
Dec 6, 2004
Messages
368
Location
Utah, USA
I've got a customer that uses frontpage and SSL. I've setup the SSL part and it's working just fine. The problem is that when I installed the FP extensions, they did not install in the private_html directory, therefore, the frontpage processing for the SSL secured forms doesn't work.

Any idea how to get this working?
 
I'm not sure but I think FPX may be incompatible with separate directory structure.

You may have to move everything from private_html to public_html, then remove the private_html directory and recreate it as a link to the public_html directory.

WARNING: be sure to make backups of all your directories first (maintaining all permissions and ownerships) so you can restore if you make an error.

Jeff
 
That worked for the SSL part of it, but the FP processing doesn't work.

Error returned in browser
<start browser error>
FrontPage Error.
User: please report details to this site's webmaster.

Webmaster: please see the server's system log for more details.
<end browser error>

system log says:
<start system log>
Dec 29 15:35:58 xxxx Microsoft FrontPage Server Extensions: Error #20015 Message: Cannot open "we443.cnf": no such file or folder. (userid ***)
Dec 29 15:35:58 xxxx Microsoft FrontPage Server Extensions: (OS Error #2 Message: No such file or directory) (userid ***)

Edited the httpd.conf file for that domain and changed the directories in that. No dice either.

This is not good. Help!
 
no dice.

same errors.

Their's got to be a way to make this work... I need it to work...

BTW, thanks for you help so far.
 
I've been told that FPX is somewhat of a black art.

There are some FPX forums where you might get some answers.

Jeff
 
Huh?

That's not quite the answer I was expecting, or hoping for...

I'm not sure what you relation to DA is, but isn't there a way to get them involved to help with a problem that I thought was supported? I've got a lot of time and $ invested into migrating to a product I thought would meet my needs. Now with this new "bug" it will turn into a lot more time and extra $$...

This really puts me in a difficult situation with my customers, and I'm not one bit happy about it.

:mad:

thanks for the tips on fpx forums.. I'll go see if anyone else has ran into a problem like this, and knows of a fix.
 
I probably should have suggested you write DA support. I will bring the post to their attention.

Jeff
 
Hello,

The frontpage installer doesn't currently install to https.

You can try running this to enable it:
Code: 
/usr/local/frontpage/version5.0/bin/owsadm.exe -o install -u [b]user[/b] -p 443 -m www.[b]domain.com[/b] -servconf /usr/local/directadmin/data/users/[b]user[/b]/httpd.conf -pw [b]password[/b] -xuser [b]user[/b] -xgroup [b]user[/b]

/usr/local/frontpage/version5.0/bin/owsadm.exe -o roleusers -c add -w / -p www.[b]domain.com[/b]:443 -n admin -u [b]user[/b]

Replace all bold words with the relevant info.
Also make sure that the private_html directory is still a directory and not a link to public_html.

If that works for you, I can add that bit of code to the frontpage installer/uninstaller if SSL is enabled for the domain.

John
 
Thank you so much for the reply. I appreciate it a TON!

The first command returned an error:

Error: An access setup description is required when creating the root web.

I ran the second one anyway, just to see if it would work still, and got an error on it as well (I thought I would though since the first one didn't work). However it did put the vti stuff in the directories, but still didn't work.

Error: The FrontPage Server Extensions are not installed on 'www.#########.com:443'

Any idea what it's talking about on the first error?
 
Sweet! That fixed the errors on install.

Both installed correctly.

However, now when try to use the form is takes me to a page that says:

Cannot run the FrontPage Server Extensions on this page: "http://www.###############.com:443/online/regforms/reg_arthritis.htm"

Any idea on that one?
 
Here are the errors from the error.log for that domain if this helps any.
[Thu Dec 30 21:03:12 2004] [error] mod_ssl: SSL handshake failed: HTTP spoken on HTTPS port; trying to send HTML error page (OpenSSL library error follows)

[Thu Dec 30 21:03:12 2004] [error] OpenSSL: error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request [Hint: speaking HTTP to HTTPS port!?]

[Thu Dec 30 21:03:12 2004] [error] [client 205.163.15.63] File does not exist: /home/######/domains/###########.com/private_html/400.shtml
Click to expand...
BTW, thank you so much for your assistance.
 
Hello,

That one looks like a client error.. connecting to the https 443 port using plain http without ssl..

First confirm that it's frontpage that is creating that error (try a few times and see if the error reproduces), then check to see if frontpage is using ssl to make the connection on 443 (not sure where that setting is in frontpage)

John
 
DirectAdmin Support said:
Hello,

That one looks like a client error.. connecting to the https 443 port using plain http without ssl..
Click to expand...
I'm not sure what you mean by a client error? You mean my IE isn't working as it should?
DirectAdmin Support said:
First confirm that it's frontpage that is creating that error (try a few times and see if the error reproduces), then check to see if frontpage is using ssl to make the connection on 443 (not sure where that setting is in frontpage)

John
Click to expand...
I tried it about 20 times and got the exact same results each time.

If I run it on the non-secure page (public_html) then it works as it's supposed to, with no errors.

I'm not sure if FP is the one procing the error or not??? :confused: I looked in the frontpage administration page (on both 80 and 443) and I don't see anywhere where you specify SSL or no SSL?

BTW, the url in the browsers address bar is:
https://www.##########.com/_vti_bin/shtml.exe/online/regforms/reg_arthritis.htm
Click to expand...
The error is:
Cannot run the FrontPage Server Extensions on this page: "http://www.##########.com:443/online/regforms/reg_arthritis.htm"
Click to expand...
Is their anyway to change this one site so it doesn't use separate directories for SSL (private_html) and non-ssl (public_html)?

In fact, I don't think the client would care if the entire site was secured (just use private as the default for 80 & 443)...

Just throwing out possible solutions, as the current server they are on will be shut down in the next couple of days so I've got to get something working as soon as possible.

Also, if it would help, I can PM you the exact URL's and any other information that might help to get this working. I can send you the forms or whatever. Just let me know and I'll do it.
 
Last edited:
Sorry to get impatient, but the server they were on has gone away so I need to get this working or find an alternate solution until we can get this working...
 
Hello,

I think the best solution is the simplest as Jeff mentioned in the very first reply. Just create a symbolic link to the public_html (or vice versa). Do all frontpage client uploads and access through regular http.

If the problem is a frontpage "tool" (ie counter or someting) running through https which isn't working.. then check your /var/log/httpd/fpexec or error_log .. or domains/domain.com.error.log for clues.

John
 
You must log in or register to reply here.
Back
Top