Clicking 'Continue with GitHub' fails
I am attending the Udemy course
React - The Complete Guide (incl Hooks, React Router, Redux)
I have followed the instructions given there.
Video number 347 (at 9:14) instructs me to go to
https://vercel.com/signup and then click Continue with GitHub,
which I did – several times.
But I always get the same message:
This user account is blocked. Contact registration#vercel.com for
more information.
My question(s)
Why did this happen? – How do I get unblocked and proceed?
My ultimate goal is to automatically deploy the NextJS project at
https://vercel.com via GitHub.
Clicking 'Continue with Email →' succeeds
After sending a few emails back and forth trying to get support, I
didn't feel much wiser, but I decided to click on Login in the
top-right corner, and then on Continue with Email →.
After confirming my email address, I got a message saying
Sign Up Successful but then nothing more happened.
So I did it once more, and this time I automatically got redirected to
the Vercel dashboard, https://vercel.com/dashboard.
Getting to the dashboard feels like a step forward, but I still don't
know how to proceed.
1
References
React - The Complete Guide (incl Hooks, React Router, Redux)
https://vercel.com/login/email
1
Going back and clicking 'Continue with GitHub' still displays the
same old message:
This user account is blocked. Contact registration#vercel.com for
more information.
Why did this happen? – How do I get unblocked and proceed?
My ultimate goal is to automatically deploy the NextJS project at
https://vercel.com via GitHub.
Since you managed to get unblocked, I will focus on building and
deploying the project at https://vercel.com.
Below I describe what worked for me.
1. Install the Vercel app at GitHub
I went to https://github.com/apps/vercel and clicked Install.
Doing so took me to a
https://github.com/apps/vercel/installations/new/permissions link.
Here too, I clicked the Install button – located in the lower-left
part of the page.
1
2. In the Vercel dashboard, get the project's code from GitHub
I was then redirected to a page at https://vercel.com/ saying
Installation Approved.
Here I clicked Go to Dashboard which took me to the Vercel
dashboard, https://vercel.com/dashboard – as shown in the last image
of your question.
In the dashboard, I clicked Create a New Project which took me to
https://vercel.com/new, with the headline
Let's build something new.
The top-most git repository, nextjs-meetups-demo, is the site I
wanted to deploy.
So I clicked its Import button.
3. Configure and deploy the project
I was now taken to a https://vercel.com/new/import page with the
headline Configure Project.
Since I was happy with all the default settings, I simply clicked
Deploy.
After building for 51 seconds, I was congratulated for having deployed
my NextJS site.
Clicking the image redirected me to the React Meetups site, finally
proving it was deployed.
2
References
Install the Vercel app at GitHub
The Vercel 'build something new' page
1
This apparently gives Vercel access to my repositories at GitHub so
that it can build and deploy any of my projects.
2
Unfortunately, my site at Vercel does not display any newly added
meetups – even though I can see in MongoDB that a meetup has been
created.
This would call for a whole new Stack Overflow question, so I won't
delve into it here.
Related
I've created a simple app, and when I open it locally works correctly. 1
When I deploy to GitHub pages, the deployment works, but for some reason the app isn't fetching the data, so I just have a navbar. 2
Does anyone know why this might be happening? I followed the instructions here: https://docs.github.com/en/pages/quickstart and selected (/root) branch.
When I tried using the /docs branch the app didn't get deployed, it just said "Your GitHub Pages site is currently being built" for a long time (> 20min)...
If helpful, here's the repo: https://github.com/ghersf91/chocostore
Thank you.
I already tried a million times and not able to figure out where I am going wrong. I tried simple static website repo. I even added parcel bundler. I just get same error message.
I even forked netlify's own demo repo. And I got same message. Why I am not able to deploy the site?
I looked at forums, blogs and even answer in this forum and I am not finding clue to this exact message. I didn't have netlify.toml file. I added that file too and I don't see any change in deployment status.
Initially I was trying to just create site online by connecting to GitHub repo. When I tried Netlify-CLI I could see some deploy action happen. But server was not render. Found a guide here: https://github.com/Tanu-N-Prabhu/Multiplication-Table-App
Followed last 3 steps under Deployment section:
Go to your Netlify Dashboard to the project. Click on Site has not yet been Deployed. Again click on Deploy Preview this will unlock the Preview Deploy which is a temporary URL.
After viewing the Preview, click on Publish deploy option to deploy your project.
Now your project is live and deployed on the internet.
These steps worked. But Javascript files were not rendering. I wonder why the whole process is so cumbersome when they advertise everything is taken care by Netlify automatically? There is no document for Site has not yet been deployed on their site and google search only leads me to Page not found forum page.
You must add the --prod.
The command should look like this: netlify deploy --prod.
This fixed it for me.
I've installed the Google Cloud Build app from Github Marketplace, and enabled it on several repositories, only to discover that enabling access for those repositories automatically starts running the Google Cloud Build "check" after every PR or push to a PR. Since some of those repositories are not actually ready for Google Cloud build, I needed to turn off the checks... I used the URL mentioned in the docs to get to the page where you can select which repositories should be connected to your GCP project, and unchecked a bunch of them... this disconnected them from the project, but, surprisingly, did not disable the Github checks! So now, there are Github checks on several repositories that just result in an error because they're not connected to any projects in Cloud Build.
Surely, it is not an uncommon use case to need a way to "disable Checks" on a per-repository basis - is there any way to do that?
(If not, consider it a requested feature if there are any Google Engineers reading!) ;)
I did talk to chat support, and the only way we could figure out to remove the checks would be to uninstall Google Cloud Build completely from the entire organization, which I don't want to do because we do have some setup that I want to keep, and I don't know how much of that configuration would have to be redone if I uninstalled it completely.
Here is a screenshot of the broken check that I can't disable:
I think there are 2 steps to disable CloudBuild,
1. Disable on CloudBuild itself. For some time I kept seeing 2 builds per push made, but disabling a trigger on CloudBuild helped fix that.
2. On Github, you can configure the Cloudbuild app to monitor a specific repo on the organization level setting.
3. If you feel a lot adventurous though and it's not solved, on the project level setting, you could delete the Webhooks integration for cloudbuild, as that's what Github notifies of each build.
It can be found within GH App installations:
https://console.cloud.google.com/gcb-github-registration
Select the GH account used for your link between Cloud Build and GH, then the GCP project you want to edit.
Here connected repositories can be edited, and in the second step (Trigger settings), the "Default GitHub Checks" can be disabled.
You can also goto settings of your repository and click installations inside settings.
And then remove Google cloud build from Installed apps and authorized github apps.
Cloud Build Triggers are still in beta, and have gone through several updates since this question was posted, but it now appears that the "Github Default Checks" are no longer hidden from management. They are now explicitly offered (but not automatically created) when connecting a repo, and you can finally view and disable (or delete) individual "Github Default Checks" on the trigger management page: https://console.cloud.google.com/cloud-build/triggers
I'll leave this as unanswered, because I'm uncertain this is how it is working for everyone, or that this answer will remain true, but if it works for you, feel free to vote up the answer!
To link GCP Project to the Github repository, create a trigger by clicking on resolve link, besides Action Required and then disable the same. For me this procedure worked out.
I created a new repo
https://github.com/Azambadar/software-developer-portfolio on GitHub and enabled my site in the settings at the master branch and it showing the following message:
Your site is ready to be published at
https://azambadar.github.io/software-developer-portfolio/
but when I click the link, it showing 404 site not found.
Repo have index.html file in the root directory and github would setup auto to this file.
Am I missing something ? How can I fix this issue?
GitHub recently experienced a significant service interruption/failure due to apparent hardware issues:
Developer platform GitHub has been down for hours due to data storage
issues. According to GitHub’s status message board, the issue began
around 10 PM ET on Sunday. Some users are facing login errors while
others are not able to see their commits.
The service is back up and running however are still recovering- in the case of Github Pages, they are still rebuilding Pages:
We have resumed Pages builds and will continue to monitor as we process a delayed
backlog of events.
You haven't done anything wrong with configuring your GitHub Projects site and it should start working within the next few hours.
Here's an example of a project:
https://github.com/storm-enroute/macrogl
The README.md of this project contains a build status image from a Jenkins running on a server somewhere else:
[](https://ci.storm-enroute.com:8080/job/public-macrogl/)
This image is rendered perfectly in Stackoverflow and Github static pages, but on the Github website it is cached to the content delivery network called Fastly. Opening the image URL shows "Not found".
Why is this happening?
How do I have the Github web interface render a markdown with such an image correctly?
How do I have the Github web interface render a markdown with such an image correctly?
The syntax is correct.
Some other project leverage such feature (see LibGit2Sharp Readme or libgit2 Readme for instance).
Why is this happening?
Few seconds ago, https://ci.storm-enroute.com:8080/job/public-macrogl/badge/icon was returning a 404 for me. It looks now fixed.
However, there's a possibility that when the CI server is offline/can't be reached, the 404 is temporarily cached by Camo and served until the cache expires.
install jenkins plugin for embeddable-build-status from: https://plugins.jenkins.io/embeddable-build-status
add to your README.md the tags you want:
Plain Link (with view)
http://URL:8080/buildStatus/icon?job=JOB_NAME
Plain Link (without view)
http://URL:8080/buildStatus/icon?job=JOB_NAME
Markdown (with view)
Build Status http://URL:8080/buildStatus/icon?job=JOB_NAME
Markdown (without view)
Build Status http://URL:8080/buildStatus/icon?job=JOB_NAME
3.Configure jenkins security to allow the status view:
Manage Jenkins -> Configure Security -> Authorization -> choose matrix-based security and check the "ViewStatus" box for the Anonymous user.
if admin user is not there, add it and give it permission to all the boxes.
For anyone else spending way more time than intended on this and wanting a little clarity on what link(s) to use after installing the Emeddable Build Status plugin:
If you navigate to the job in the Jenkins (jenkins_home >> repo >> project >> branch), there's a "Emeddable Build Status" widget you can click on the left pane, and it'll show list exactly what links you can use for your specific jobs.
The following URL structure might also get you to the embeddable build status page:
https://<jenkins_host>/job/<github_owner_or_org>/job/<github_repo_name>/job/master/badge/
Update: I had a similar issue. It turned that the cache server requires the image to be hosted behind a HTTPS, with a fully valid SSL certificate chain (CA(s) + cert). Once your server provides the full cert chain, github will display your badge.