These are chat archives for collectiveaccess/support

13th
Feb 2016
alberg214
@alberg214
Feb 13 2016 15:33
Good morning
CollectiveAccess
@collectiveaccess
Feb 13 2016 15:41
hi
I'll have time later today to look into your problem
You're hosting this on Bluehost no?
alberg214
@alberg214
Feb 13 2016 15:42
yes
CollectiveAccess
@collectiveaccess
Feb 13 2016 15:42
And it's shared hosting?
alberg214
@alberg214
Feb 13 2016 15:42
unfortunately yes
CollectiveAccess
@collectiveaccess
Feb 13 2016 15:42
ok
Is there any way I can get access to the machine, at least for today?
alberg214
@alberg214
Feb 13 2016 15:42
sure - let me set you up with ssh
CollectiveAccess
@collectiveaccess
Feb 13 2016 15:42
I can't reproduce the issue and I suspect it's something with their hosting set up
alberg214
@alberg214
Feb 13 2016 15:42
hang on a sec
CollectiveAccess
@collectiveaccess
Feb 13 2016 15:43
people have run on BlueHost before so it should be possible
obviously don't send credentials here
it's public
alberg214
@alberg214
Feb 13 2016 15:43
yeah - was working
CollectiveAccess
@collectiveaccess
Feb 13 2016 15:43
you can email me at seth@collectiveaccess.org
thanks
we'll get you working yet...
alberg214
@alberg214
Feb 13 2016 15:43
great - thank you very much
CollectiveAccess
@collectiveaccess
Feb 13 2016 15:44
I'll also need a CA login that works
alberg214
@alberg214
Feb 13 2016 15:44
ok - will send that too
CollectiveAccess
@collectiveaccess
Feb 13 2016 15:45
thanks
I'll be in touch later today
alberg214
@alberg214
Feb 13 2016 15:48
ok - sending an ssh key
pass is cacaca (seems safe to give to you since not posting the key itself here)
there is an asterisk between the three "ca"s -
markdown issue i guess
CollectiveAccess
@collectiveaccess
Feb 13 2016 17:39
got it thanks