bad function name
in ash shell I cant do this I cant name a function with a period in its name
wild card domain letsencrypt, Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. You may need to use an authenticator plugin that can do challenges over DNS.
https://community.letsencrypt.org/t/you-may-need-to-use-a-different-authenticator-plugin/115026
Instagram Graph api
Get Facebook instagram access token Create instagram basic display app and Get instagram basic display access token Switch instagram personal account to business account or creator account Link facebook account to Instagram Invite your self to be a instagram tester instagram.com Get business account id https://stackoverflow.com/questions/50709794/cant-get-instagram-business-account-id-through-facebook-graph-api or Get business or[…]
Can’t Load URL: The domain of this URL isn’t included in the app’s domains. To be able to load this URL, add all domains and subdomains of your app to the App Domains field in your app settings.
this is the url its checking it against. now to figure out why its http instead of https changed it to
Cross-site request forgery validation failed. Required param “state” missing from persistent data.
https://stackoverflow.com/questions/44684473/facebook-sdk-error-cross-site-request-forgery-validation-failed-required-param
Instagram: useragent mismatch, Get user profile details
https://github.com/postaddictme/instagram-php-scraper/issues/544
Puppeteet: error: Error: Failed to launch the browser process! api | 2022-09-16T14:15:42.542608789Z /home/docker/src/node_modules/puppeteer/.local-chromium/linux-901912/chrome-linux/chrome: error while loading shared libraries: libxshmfence.so.1: cannot open shared object file: No such file or directory
https://stackoverflow.com/questions/68646577/puppteer-cannot-open-shared-object-file-libxshmfence-so-1
Puppeteer chrome stalling, .newPage()
https://stackoverflow.com/questions/66402124/puppeteer-blocked-at-newpage
publishing npm package: 404 Not Found
I then changed the version in the package.json to v1.0.1, then when I published it worked then I deleted v1.0.1 and then published v1.0.0 and then it worked. very wierd. also placiing this line in the packages .npmrc worked Also found this fix you either need to use a equal[…]