Microca.st

Follow

[email protected] [email protected]

Triad/NC

My main account is at https://io.jrobb.org/jrobb This is a backup account in case something goes wrong there. http://www.jrobb.org/contact/

  • 2014-10-08T20:16:35Z via Microca.st Web To: Public CC: Followers

    my internet connection is out at home, and no idea when it'll be fixed.
    so....I'm here for now!

    ezeq likes this.

    Back at home in a week or so!

    X11R5 at 2014-10-09T15:33:50Z in Hawthorne, Nevada

  • 2014-09-01T12:43:48Z via Microca.st Web To: Public CC: Followers

    bah.  I'm getting "Unable to retrieve proxy data" errors.

    I've got pump.io running on 127.0.0.1
    nginx "pumpbackend" set to 127.0.0.1:4443

    I'm missing something.

  • pump server changes

    2014-09-01T02:13:58Z via Dianara To: Public CC: Followers

    so I've got my pump working on my home server behind the proxy, it seems. Would it really bork up my account if I use my same database/webfinger/secret/everything just a new host? and now behind a proxy instead of direct, does that matter?

    I think if the domain name is the same you should be able to keep all of those things.

    Ryan Weal at 2014-09-01T03:04:20Z

    [email protected] likes this.

    >> Ryan Weal:

    “I think if the domain name is the same you should be able to keep all of those things.”


    that's my thinking as well, I'd just hate to to mess it up and move onto my 4th(?) pump. If no one comes up saying it's a bad idea I'll put it live tomorrow

    [email protected] at 2014-09-01T03:06:17Z

  • 2014-08-31T22:07:43Z via Microca.st Web To: Public CC: Followers

    I'm attempting to use my backups to setup my pump on my home server.
    when I launch pump, I am getting bind errors.

    As I'll have to run behind a proxy, I'm using the computer's IP and port 9443. 
    can the pump server not bind to the same IP that nginx is bound to?
    oops, I had bounce = true so it was trying to use port 80.

    [email protected] at 2014-08-31T22:11:08Z

  • 2014-08-31T21:09:36Z via Microca.st Web To: Public CC: Followers

    my vps will be down at least until tomorrow, so in the meantime i'll have to use my backup pump here (and gnu social)

    Did they at least clarify why your account was suspended?

    JanKusanagi at 2014-08-31T21:20:25Z

    @jan yes, I blew through my 3TB bandwidth limit.

    I had a lot of linux and BSD ISOs seeding, and never really thought much about it.  I guess I had too many this month!

    [email protected] at 2014-08-31T21:50:08Z

  • 2014-08-31T18:10:43Z via Microca.st Web To: Public CC: Followers

    chicagoVPS has suspended my account for some reason, so my pump which is hosted there is down.  :-/

  • 2014-06-25T00:51:12Z via Microca.st Web To: Public CC: Followers

    my owncloud running on my home server stopped working today for some reason.

    I'm at owncloud 6.0.3, and all of a sudden I get 502 bad gateway errors.

    in my nginx log the error is:

    2014/06/24 20:18:46 [crit] 1945#0: *14 connect() to unix:/var/run/php5-fpm.sock failed (13: Permission denied) while connecting to upstream
     request: "HEAD /remote.php/webdav/InstantUpload/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:",


    anyone have any ideas what would cause this?
    looks like the permissions, as the socket is owned and group'd root:
    srw-rw---- 1 root        root          0 Jun 24 20:45 php5-fpm.sock


    this may be relevant, but my settings are already like that as far as I can tell.  except user and group are www-data

    hm

    [email protected] at 2014-06-25T01:03:20Z

    I was wrong -- these two lines were commented out.

    listen.owner = nginx
    listen.group = nginx
    now everything is working again.
    it is weird that everything was running fine until it wasnt, with no changes like that.




    [email protected] at 2014-06-25T01:10:09Z

    I have noticed that certain distros will change config files without asking during upgrades. Had a Samba server at home that suddenly decided it was part of a generic workgroup.

    [email protected] at 2014-06-25T02:20:30Z

  • 2014-06-25T00:49:23Z via Microca.st Web To: Public CC: Followers

    vps is down for a kernel patch.  joys of openvz

  • 2014-06-21T21:31:51Z via Microca.st Web To: Public CC: Followers

    my vps is down.  running, but maybe the node is being DDoS'ed or otherwise being abused (again).

    :-(
    haha

    ~ $ ping jrobb.org
    PING jrobb.org (192.210.205.174) 56(84) bytes of data.
    ^C
    --- jrobb.org ping statistics ---
    896 packets transmitted, 0 received, 100% packet loss, time 902159ms


    [email protected] at 2014-06-21T21:34:35Z

  • 2014-06-21T16:22:46Z via Microca.st Web To: Public CC: Followers

    I shut my pump down for a little bit for some maintentance:  ssl cert renewal, merge with upstream/master, etc.

    Christopher Allan Webber , Evan Prodromou like this.

    compiling nodejs 10.29 now :)

    [email protected] at 2014-06-21T16:23:09Z

    I just did that yesterday :-)

    sazius at 2014-06-21T16:26:39Z

    [email protected] likes this.

  • 2014-04-28T12:36:02Z via Microca.st Web To: Public , jrobb , jrobb CC: Followers

    VPS went down again (chicagoVPS)

    though not actually down-- just non-responsive for a couple of minutes. that was odd. 
    I sent an email to the billing department inquiring about the compensation that they said we were supposed to get for the large outage a year or so ago that resulted in data loss. 
    I mean-- at $5/month I don't expect too much, but I want them to uphold what they say they will do at the least. Also, I asked for some data showing the uptime over the last couple of years for my node -- I highly doubt their "99.9% uptime".

    Currently I cannot ssh in, and my pump doesn't appear to be working now. :-/
    I liked having the vps to kind of spread out my resources, but I think now I'm motivated to migrate to a home server again.

    [email protected] at 2014-04-28T12:43:16Z

    X11R5 likes this.

    at least my mediagoblin server is still up!

    [email protected] at 2014-04-28T12:46:06Z

  • 2014-04-15T16:10:53Z via Microca.st Web To: Public CC: Followers

    and now the vps is back up.  someone was crashing my node, they kicked whoever it was off pretty quickly

    jrobb shared this.

  • 2014-04-15T15:57:04Z via Microca.st Web To: Public CC: Followers

    my vps is down.... apparently.

  • now we are getting somewhere

    2014-03-27T02:46:15Z via Pumpa To: Public CC: Followers

    I did this:

    $ chmod 700 ~/
$ chmod 700 ~/.ssh
$ chmod 600 ~/.ssh/authorized_keys

    And now my rsa key is failing, but the ecdsa is prompting for my passphrase (and lets me in!)

    X11R5 shared this.

    step by step =)

    JanKusanagi at 2014-03-27T02:52:05Z

    it's not accepting the keys from my phone, though...but that's a minor detail at this point :)

    [email protected] at 2014-03-27T02:58:29Z

    and now it works as well!

    [email protected] at 2014-03-27T03:02:45Z

    Victory! \o/

    JanKusanagi at 2014-03-27T03:06:39Z

    jrobb likes this.

  • ...investigating...

    2014-03-27T02:11:21Z via Pumpa To: Public CC: Followers

    ahha! I was able to get the web console to work in Firefox (but not in Chromium). I've re-enabled password login, and I can access the vps again normally.

    I guess I will have to either re-add my keys, or maybe the permissions got borked somehow.

    X11R5 likes this.

    hmm...

    sshd[1595]: Authentication refused: bad ownership or modes for directory

    [email protected] at 2014-03-27T02:42:46Z

  • 2014-03-20T02:00:35Z via Microca.st Web To: Public CC: Followers

    testing the pump2tweet.com bridge

    well...I didn't have it turned on.

    jrobb at 2014-03-20T02:06:07Z

  • 2014-03-12T14:42:49Z via Pumpa To: Public CC: Followers

    baha! got it working. I'm not sure if it is 100%, but I've got the basics and can login, and uploaded my avatar.

    This is a good sign.

    X11R5 likes this.

    jrobb shared this.

  • 2014-03-12T14:23:27Z via Microca.st Web To: Public CC: Followers

    I think ... my pump is broken.  I've got lots of errors and can't login.  :-(

    If I don't work this out, I'll just create a new pump tonight w/ a slightly different domain.  I think this'll be #4

  • 2014-03-12T12:52:09Z via Microca.st Web To: Public CC: Followers

    for some reason the debian x64 image never would work properly, so I just used the newest ubuntu version they had

    ... 12.10.  so now I'm upgrading this before I go much further on the vps setup.  

    I expect that my pump will be back online tomorrow.
    now running 13.10 "saucy"

    [email protected] at 2014-03-12T13:06:25Z

  • 2014-03-12T03:24:24Z via Microca.st Web To: Public CC: Followers

    I've got my pump almost entirely setup, intact w/ my last setup, but I'm not leaving it running yet.

    however, whenever I start it up, I get a prompt for "PEM passphrase".   -- does this mean I've got my ssl cert/key stuff not setup correctly?
    I'll look at it tomorrow, time for bed

    [email protected] at 2014-03-12T03:34:51Z

    I suspect that you'll need to create a version of your cert/key that is not password protected. I had to do something similar for Apache recently.

    [email protected] at 2014-03-12T04:13:26Z

    Douglas Perkins likes this.

    I grabbed some files from my backup, but I figured that was already done.  guess not!  I'll re-generate them and see how that goes.

    thanks

    [email protected] at 2014-03-12T11:51:10Z