New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get it to work with proxies #488

Closed
balupton opened this Issue Apr 18, 2013 · 24 comments

Comments

Projects
None yet
@balupton
Member

balupton commented Apr 18, 2013

http://stackoverflow.com/q/15942403/130638

Current workaround, agree to the TOS manually by filling in your ~/.docpad.cson or ~/Dropbox/.docpad.cson file yourself:

{
  name: "Your name"
  email: "Your email"
  username: "Your username"
  subscribed: true
  subscribeTryAgain: null
  tos: true
  identified: true
}

HOWEVER

Please post a comment below on whether or not you use sudo with node. If you do, it means node is installed globally and probably shouldn't be, you can use the install intructions here http://learn.bevry.me/node/install to avoid permission issues. If these better install instructions fix it, let us know.


Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

@esteinborn

This comment has been minimized.

Show comment
Hide comment
@esteinborn

esteinborn Apr 22, 2013

When adding this to a docpad.cson in the ROOT of my docpad site, when running docpad run it still prompts me to accept ToS, so I know its not working correctly.

It's supposed to be docpad.cson not .docpad.cson right? (second is a dotfile)

I'm behind a pretty nasty firewall and cannot run this without this feature working.

When adding this to a docpad.cson in the ROOT of my docpad site, when running docpad run it still prompts me to accept ToS, so I know its not working correctly.

It's supposed to be docpad.cson not .docpad.cson right? (second is a dotfile)

I'm behind a pretty nasty firewall and cannot run this without this feature working.

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Apr 22, 2013

Member

Hey mate, perhaps I wasn't that clear. ~ is your user directory not your project directory, so for me because I have dropbox installed that file is located at /Users/balupton/Dropbox/.docpad.cson however if I didn't have dropbox installed it would be at /Users/balupton/.docpad.cson - this file is different from your typical project configuration file, as it applies to all your projects, or rather, it applies to you.

Member

balupton commented Apr 22, 2013

Hey mate, perhaps I wasn't that clear. ~ is your user directory not your project directory, so for me because I have dropbox installed that file is located at /Users/balupton/Dropbox/.docpad.cson however if I didn't have dropbox installed it would be at /Users/balupton/.docpad.cson - this file is different from your typical project configuration file, as it applies to all your projects, or rather, it applies to you.

@esteinborn

This comment has been minimized.

Show comment
Hide comment
@esteinborn

esteinborn Apr 22, 2013

OOOOOOOOH.

I forgot that I had dropbox installed on my work machine previously. So I copied the file there and it worked! Brilliant!

Thanks for the super quick reply!

+1 for auto-detecting dropbox.

OOOOOOOOH.

I forgot that I had dropbox installed on my work machine previously. So I copied the file there and it worked! Brilliant!

Thanks for the super quick reply!

+1 for auto-detecting dropbox.

@jjagoda

This comment has been minimized.

Show comment
Hide comment
@jjagoda

jjagoda Apr 22, 2013

@balupton Your last comment clears a lot. Now it works. Thanks!

jjagoda commented Apr 22, 2013

@balupton Your last comment clears a lot. Now it works. Thanks!

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Apr 23, 2013

Member

Awesome. Glad the workaround works :) 👍 I wonder what the proper fix for this is... In about 2 weeks would one of you be willing to let me remote in so I can debug? That would be amazing. Alternatively, if someone can submit a pull request on this, that would be grand. Cheers everyone.

Member

balupton commented Apr 23, 2013

Awesome. Glad the workaround works :) 👍 I wonder what the proper fix for this is... In about 2 weeks would one of you be willing to let me remote in so I can debug? That would be amazing. Alternatively, if someone can submit a pull request on this, that would be grand. Cheers everyone.

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Apr 23, 2013

Member

I've also added mention of this to the troubleshoot guide http://docpad.org/docs/troubleshoot and added mention of the global configuration file to the config guide http://docpad.org/docs/config#global-configuration-file :)

Member

balupton commented Apr 23, 2013

I've also added mention of this to the troubleshoot guide http://docpad.org/docs/troubleshoot and added mention of the global configuration file to the config guide http://docpad.org/docs/config#global-configuration-file :)

@s2zaman

This comment has been minimized.

Show comment
Hide comment
@s2zaman

s2zaman Sep 19, 2013

That one works.......and is OK 👍

s2zaman commented Sep 19, 2013

That one works.......and is OK 👍

@thegreatsunra

This comment has been minimized.

Show comment
Hide comment
@thegreatsunra

thegreatsunra Nov 12, 2013

Just experienced this issue while behind a proxy and trying to run DocPad for the first time. Running docpad would trigger the TOS message, but any response would quit DocPad and return to the command prompt with no message about what happened.

I got lucky finding this thread, as I had no idea it was being triggered by a proxy issue.

As an interim fix, perhaps DocPad should fire a message with the URL of this thread if the remote TOS query fails.

The good news is, the workaround works flawlessly!

Just experienced this issue while behind a proxy and trying to run DocPad for the first time. Running docpad would trigger the TOS message, but any response would quit DocPad and return to the command prompt with no message about what happened.

I got lucky finding this thread, as I had no idea it was being triggered by a proxy issue.

As an interim fix, perhaps DocPad should fire a message with the URL of this thread if the remote TOS query fails.

The good news is, the workaround works flawlessly!

@brandon-arnold

This comment has been minimized.

Show comment
Hide comment
@brandon-arnold

brandon-arnold Jun 24, 2014

I just required the same fix on Fedora 20. Is it because I had a ~/Dropbox before installing docpad, and it doesn't know to automatically put .docpad.cson there?

Anywho, FYI.

I just required the same fix on Fedora 20. Is it because I had a ~/Dropbox before installing docpad, and it doesn't know to automatically put .docpad.cson there?

Anywho, FYI.

@greduan

This comment has been minimized.

Show comment
Hide comment
@greduan

greduan Jun 24, 2014

Contributor

@brandon-arnold well if the Dropbox folder was already there then I don't see why it would be a problem. You need to accept the ToS once before with the Dropbox folder, or your home folder if there's no Dropbox, so that it is not repeated next time.

Contributor

greduan commented Jun 24, 2014

@brandon-arnold well if the Dropbox folder was already there then I don't see why it would be a problem. You need to accept the ToS once before with the Dropbox folder, or your home folder if there's no Dropbox, so that it is not repeated next time.

@twoolf

This comment has been minimized.

Show comment
Hide comment
@twoolf

twoolf Jul 8, 2014

just a note that this resolved for me on a Macbook when I added the .docpad.cson as mentioned above --

twoolf commented Jul 8, 2014

just a note that this resolved for me on a Macbook when I added the .docpad.cson as mentioned above --

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Jul 9, 2014

Member

I restarted the helper service the other day.

For all those reporting errors with the TOS, do you usually use "sudo" with either npm, node, or docpad? Perhaps it's a permissions issue.

Member

balupton commented Jul 9, 2014

I restarted the helper service the other day.

For all those reporting errors with the TOS, do you usually use "sudo" with either npm, node, or docpad? Perhaps it's a permissions issue.

@twoolf

This comment has been minimized.

Show comment
Hide comment
@twoolf

twoolf Jul 9, 2014

That could be the problem on my end. I initially re-installed npm/node on
reading about the possibility of permission issues in your start guide.
But, its entirely possible that it didn't resolve all the permissions
issues.

On Tue, Jul 8, 2014 at 8:54 PM, Benjamin Arthur Lupton <
notifications@github.com> wrote:

I restarted the helper service the other day.

For all those reporting errors here, do you usually use "sudo" with either
npm, node, or docpad? Perhaps it's a permissions issue.


Reply to this email directly or view it on GitHub
#488 (comment).

twoolf commented Jul 9, 2014

That could be the problem on my end. I initially re-installed npm/node on
reading about the possibility of permission issues in your start guide.
But, its entirely possible that it didn't resolve all the permissions
issues.

On Tue, Jul 8, 2014 at 8:54 PM, Benjamin Arthur Lupton <
notifications@github.com> wrote:

I restarted the helper service the other day.

For all those reporting errors here, do you usually use "sudo" with either
npm, node, or docpad? Perhaps it's a permissions issue.


Reply to this email directly or view it on GitHub
#488 (comment).

@arafalov

This comment has been minimized.

Show comment
Hide comment
@arafalov

arafalov Jul 19, 2014

Just had this happen with a new install under Vagrant and hashicorp/precise32. Global installs for node/npm. The ~/.docpad.cson work around worked.

Not sure how it could be proxy given that things worked fine from inside VM to install Node, etc.

Edit: also happened on Centos8 droplet on DigitalOcean.

Just had this happen with a new install under Vagrant and hashicorp/precise32. Global installs for node/npm. The ~/.docpad.cson work around worked.

Not sure how it could be proxy given that things worked fine from inside VM to install Node, etc.

Edit: also happened on Centos8 droplet on DigitalOcean.

@insanity54

This comment has been minimized.

Show comment
Hide comment
@insanity54

insanity54 Jul 22, 2014

Had this happen on my chunkhost vps running debian. docpad run would bring up the TOS prompt then silently exit. Workaround did it's thing.

Had this happen on my chunkhost vps running debian. docpad run would bring up the TOS prompt then silently exit. Workaround did it's thing.

This was referenced Aug 20, 2014

@bdenham

This comment has been minimized.

Show comment
Hide comment
@bdenham

bdenham Sep 9, 2014

Just wondering if I have a deeper install issue....For me, the .docpad.cson file was never created anywhere. Is this the case for others? I will create one at my user root folder ~ to see if that solves the issue and report back. I'm running OSX 10.9.4 and had to use sudo for updating/installing npm.

bdenham commented Sep 9, 2014

Just wondering if I have a deeper install issue....For me, the .docpad.cson file was never created anywhere. Is this the case for others? I will create one at my user root folder ~ to see if that solves the issue and report back. I'm running OSX 10.9.4 and had to use sudo for updating/installing npm.

@bdenham

This comment has been minimized.

Show comment
Hide comment
@bdenham

bdenham Sep 9, 2014

Well, apparently, my installations of node.js or something else is fubar. Adding the missing .docpad.cson file did not work. I think I'll just uninstall node.js completely and try from scratch again.

bdenham commented Sep 9, 2014

Well, apparently, my installations of node.js or something else is fubar. Adding the missing .docpad.cson file did not work. I think I'll just uninstall node.js completely and try from scratch again.

@greduan

This comment has been minimized.

Show comment
Hide comment
@greduan

greduan Sep 9, 2014

Contributor

Suggest installing it using NVM. :) https://github.com/creationix/nvm

Contributor

greduan commented Sep 9, 2014

Suggest installing it using NVM. :) https://github.com/creationix/nvm

@guaka

This comment has been minimized.

Show comment
Hide comment
@guaka

guaka Feb 16, 2015

I am NOT behind a proxy. Still this issue helped me get further.

I suggest giving DocPad a --verbose option to allow people to see what's going on.

guaka commented Feb 16, 2015

I am NOT behind a proxy. Still this issue helped me get further.

I suggest giving DocPad a --verbose option to allow people to see what's going on.

@marcusstenbeck

This comment has been minimized.

Show comment
Hide comment
@marcusstenbeck

marcusstenbeck Aug 27, 2015

No sudo, this was the only thing that worked.

No sudo, this was the only thing that worked.

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Aug 27, 2015

Member

@guaka would --verbose be different than the already existent --debug flag?

Member

balupton commented Aug 27, 2015

@guaka would --verbose be different than the already existent --debug flag?

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Aug 27, 2015

Member

@marcusstenbeck interesting... what was the precise issue you were facing?

Member

balupton commented Aug 27, 2015

@marcusstenbeck interesting... what was the precise issue you were facing?

@marcusstenbeck

This comment has been minimized.

Show comment
Hide comment
@marcusstenbeck

marcusstenbeck Aug 31, 2015

@balupton I was getting the perpetual TOS statement.

@balupton I was getting the perpetual TOS statement.

@balupton

This comment has been minimized.

Show comment
Hide comment
@balupton

balupton Jul 20, 2018

Member

Closing due to age. Ecosystem has likely fixed this. Try again with v6.80 or later.

Member

balupton commented Jul 20, 2018

Closing due to age. Ecosystem has likely fixed this. Try again with v6.80 or later.

@balupton balupton closed this Jul 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment