Question: I'm currently generating documentation on one machine, and publishing it to a web server using the following commands in a script:

```
net use "\\someShare" PASSWORD /user:username
del /S /Q "\\someShare"
xcopy /E /Y Documentation\html\* "\\someShare\"

```

However, it feels like a really bad idea to have a password as plain text in the script, so I'm looking for alternatives to my current solution. Ideas?

I definitely would appreciate a solution that uses some kind of access control, as many different people should be allowed to publish their own documentation to the web server, but not mess with each other's docs.

Answer: 
This symptom will crop up if you are used to using Puppet under Nginx/Passenger and you upgrade to passenger 5.0+. I found the solution [here](https://plus.google.com/110600731585460508682/posts/j7EucNY5bGG).

Passenger 5.0 has replaced "passenger\_set\_cgi\_param" with "passenger\_set\_header" which, if you've made it this far, you've figured out. What you might've missed however is that "passenger\_set\_header" automatically prepends the HTTP\_ to the value, so you'll need to remove it from your HTTP\_X\_CLIENT\_S\_DN and HTTP\_X\_CLIENT\_VERIFY lines.
First of all I would check what is the status of the puppetmaster - it might be either selinux configuration or port 8140 is listening to "httpd".
Try checking the output of `netstat -anpl | grep 8140`

On puppetmaster try to run `sudo puppet master --verbose --no-daemonize`

If the puppet master starts with no any errors you may have to focus on puppet agent.