+94
Save

[Update] Server Migration & Maintenance Complete!

Hi everyone!

We have now (as of 4am PST) completed our server migration and updates, for those of you who see the website live and can read this message it means that your DNS info has already been updated. However it may take up to 48 hours for some ISPs to update their DNS info, so if you have a friend that cannot access the site please let them know that it's simply a matter of their ISP updating to the new DNS information.

We hope the new changes are relatively glitch free, we spent countless hours testing everything to make sure everything is working as intended. If you do however find an issue that you feel may be caused by this migration, please be sure to report it in the comments below. We will be checking into this thread on a regular basis to see if we missed any bugs.

Thanks everyone for being so patient! We are happy to be back online!

8 years ago by drunkenninja with 35 comments

Join the Discussion

  • Auto Tier
  • All
  • 1
  • 2
  • 3
Post Comment
  • SevenTales
    +13

    So far, everything is awesome. It's quicker and smoother! Thanks for all the work you put in here guys.

  • laebshade
    +10

    Your PHP config is now slightly different; I'm receiving errors/warnings on the front page:

    http://imgur.com/7K7zwrr

    A production environment should never display errors or warnings and should log them only.

    • drunkenninja
      +6

      Yep, we are fully aware of this problem, working on it now. Thanks for the heads up.

    • spaceghoti
      +3

      I'm getting this error on any image or video preview I encounter.

  • MePLUR
    +7

    You could also tell your friend to use Google's public DNS servers.

    So far, the site does feel a little snappier. Not sure if it's because there aren't many people on at the moment.

    • Boudicca
      +6

      Snappier! I saw what you did there

      • MePLUR
        +4

        Bwahahaaha... I'm subconsciously cleverer than I realise :D

    • SevenTales
      +4

      Could be, but I browse at this time of the day a lot, and it feels a lot quicker than before, so barring the possibility of a placebo effect, I'm pretty sure it's optimizations and server change :P

  • ThenHeSaid
    +7

    Sorry for leaving this in the wrong place if I am. Is there a thread or tribe devoted to issues you're having with the site? I can't get any of my computers to remember me on Snapzu, despite checking the "remember me" box. Any help you can offer?

    • laebshade (edited 8 years ago)
      +6

      That's a known problem discussed over at /t/ideasforsnapzu I believe. The short answer is, the PHP framework used doesn't currently support staying logged in at multiple devices. It'll take modifications for that to work.

      The long answer is suspected to be: a unique hash of a user is stored in the database, based on their IP address and other information. When you log in on another device, it overwrites this hash with that new login, effectively logging out the previous user.

      -- Edited for inaccuracies

      • tehdiplomat
        +2

        Ah thanks for the explanation, I was suspicious something like that was going on, but wasn't sure.

  • capoti
    +5

    Excellent work as always. Thank you.

  • fewt
    +4

    Everything seems much more responsive, thanks for all of your work!

  • hxxp
    +4

    Loving it. So fast again!

  • FivesandSevens
    +4

    I've only noticed one thing so far: as far as I can tell, my reputation score hasn't updated with info from yesterday yet. Not a big deal, but I guess it qualifies as a bug.

    • drunkenninja
      +2

      It is very likely since during the migration we disabled all automatic updates and processes like cron jobs. Since reputation updates at night, and our migration was being done at around the same time there is a good chance that the update did not run. Please give it 24 hours and your reputation score will update as it should, if not, be sure to let us know!

  • canuck
    +3

    So how long till there is enough users to have to upgrade again?

    • messi
      +2

      Depends on what reddit does.

  • microfracture
    +2

    Congrats on the upgrades. Everything is running nice and quick. :D

  • manix
    +2

    Another good day at snapzu.

  • FrootLoops (edited 8 years ago)
    +2

    The snap type selection screen seems broken: http://i.imgur.com/rg3T22s.png @ /u/drunkenninja

    • drunkenninja
      +4

      Interesting, I am unable to repeat this issue. Would you be able to do a cache clear and try hard refreshing? It may be to do with old files stored in your browser. I tried from 3 different devices, the popover loads correctly for me on everyone of them. Either way, this is of course a concern so if this can be repeated I will get right on it to fix it. Thanks for taking the time to report the issue.

      • FrootLoops (edited 8 years ago)
        +3

        Well this is strange.

        I tried cleaning the cache again (tried it before) and it's still the same.

        I even tried it in chromium and i have exactly the same problem there.

        Then i tried a different firefox profile and it works correctly there.... i have no idea what going on.

        edit: Well, i deleted the cache in the new firefox just for fun and now i get the same wrong behavior there. So it's reproducible in all my browsers.

        I noticed some css rules are not applied in the browsers where it does not work:

        These are missing:

        .iFrame .snapTypeList li label input[type="radio"] + .radio-helper { height: 36px; line-height: 36px; padding: 0px 14px; display: block; background: #EEE none repeat scroll 0% 0%; color: #000; border-radius: 4px; }

        .iFrame .snapTypeList li label { cursor: pointer; }

        They are located in: style_popup.css

        I then noticed that in the browsers where it does not work a different style_popup.css is loaded. It has 974 rules there, while the version that works has 993 rules.

        As i said, i deleted the caches in firefox and chromium multiple times (+ restart). I have never seen something like this before. :) Maybe you have an idea what's going on?

        Tested in Firefox 39 and chromium Version 44.0.2403.107 (64-bit) both on linux.

        • drunkenninja (edited 8 years ago)
          +1

          I will look into this issue. Lets continue debugging via PM. I will PM you if I find the problem, will keep you updated.

          • FrootLoops
            +2

            ok, or irc, i can stay up a little bit longer.

  • lgramlich
    0

    Where do I send my DMCA notice, to stop your users from stealing and publishing my work?