You may have come across a 404 error on flixel.com before and wondered why. The most common incidents resulting in a 404 error on our website are from:

  • Sharing a private cinemagraph
  • Trying to sign in after a username change or expired session


Privacy Settings

Private cinemagraphs cannot be shared. If you want to share your cinemagraph with others using the URL or embed code, your privacy setting must be public or shareable. 

If your cinemagraph is set to PUBLIC:

  • it can be shared in Flixel galleries and social networks
  • it can be shared using the embed code (unless hidden) and URL 
  • viewers can see it on your public profile

If your cinemagraph is set to SHAREABLE:

  • it will not appear in Flixel galleries and social networks 
  • it can be shared using the embed code (unless hidden) and URL 
  • viewers will not see it on your public profile

Go to your profile and select the cinemagraph you wish to change the settings for. Click Edit, select Public or Shareable, and save your changes to share your cinemagraph. 


Signing In After Username Change

If a 404 error appears when trying to sign in on flixel.com after a username change or expired session, clear your browser cache and cookies.

Clearing your browser cache and cookies on Safari:

  1. Open Safari
  2. Click on the Safari menu at the upper left corner of your screen
  3. Click Preferences
  4. Click on the Privacy tab
  5. Click Manage Website Data...
  6. Search for flixel.com 
  7. Click Remove All
  8. Click Done

Clearing your browser cache and cookies on Chrome:

  1. Open Chrome
  2. Click on the Chrome menu at the upper left corner of your screen
  3. Select Preferences
  4. Click Advanced at the bottom of the page
  5. Select Clear Browsing Data under Privacy and Security 
  6. Check Cached images and files and Cookies and other site data
  7. Choose to clear items from the beginning of time
  8. Select Clear Browsing Data

After clearing your browser cache and cookies, try signing in with your Flixel ID on flixel.com. If the problem persists, let us know

Did this answer your question?