Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. "Failed to parse origin for CORS" when trying to add a Payment method

"Failed to parse origin for CORS" when trying to add a Payment method

Scheduled Pinned Locked Moved Solved Support
cors
3 Posts 2 Posters 233 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E Offline
    E Offline
    ekkeguembel
    wrote on last edited by joseph
    #1

    I get a "Failed to parse origin for CORS" when trying to add a Payment method via https://api.cloudron.io/api/v1/stripe/paymentmethods/checkout-session-create?accessToken=***

    (might this related to using the wrong NodeJS version?)

    1 Reply Last reply
    1
    • nebulonN Offline
      nebulonN Offline
      nebulon
      Staff
      wrote on last edited by nebulon
      #2

      This usually means some browser extension or privacy setting blocks the cross origin request.

      Can't see how this can be related to a nodejs version, isn't there only your browser and our backend appstore server involved?

      1 Reply Last reply
      1
      • E Offline
        E Offline
        ekkeguembel
        wrote on last edited by
        #3

        I'd agree, it's only that we have have that other issue going on and I wanted the "full disclosure" 😉

        But sure enough, switching to a different browser help.
        FYI the issue was on Safari (MacOS Sonoma, latest)

        For here: CLOSE 🙂

        1 Reply Last reply
        1
        • nebulonN nebulon marked this topic as a question on
        • nebulonN nebulon has marked this topic as solved on
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Bookmarks
        • Search