Server Error 500 when proposing a change to a project (via web)

Hi - I’m receiving this generic 500 server error when trying to propose a change to a project. It’s a project I don’t have edit access to so I believe it would create a new project and then a pull request. Not sure what to do.

Was trying to edit this: https://github.com/meshtastic/Meshtastic/tree-save/master/website/docs/software/community/atak.md

when I open that link (and being logged into my GH account) I get:

You need to fork this repository to propose changes.

Sorry, you’re not able to edit this repository directly—you need to fork it and propose your changes from there instead.

if you’re landing directly on the error 500 page then something is definitely not working right.

You might consider cleaning your browser cache, just in case there are some cookies problems, and then try again the operation (ensuring you’re logged into your GH account).

2 Likes

OK, I forked it and created my own repo, and tried to make the change but had the same error. I tried it on Firefox, Chrome, and even on mobile, with the same results.

What are you clicking on, exactly, before the 500 error page?

Are you now trying to change the atak.md document via GitHub’s browser UI?

Just to be clear we’re on the same wavelength here, to edit that file you should now open it in your own fork:

The page at the above link should show correctly. You should now be able to click on the Edit button on the bar above the file (pencil icon), which should allow you directly edit the file in the browser.

PS. If you’re intending to propose your changes to the original (upstream) repository, you should then first create a new branch on your repository fork, do your changes to the atak.md file there, and then open a pull request on the upstream repository.

If you edit the file directly on the master branch of your fork, you’ll end up with your fork being out-of-synch with the upstream repository (i.e. diverging) and then you won’t be able to update your fork to mirror the original (i.e. fetch and merge changes from it into your fork) in the future. Also, if your pull request ends up being processed after some new changes were applied to the upstream repo, you’ll be asked to update your fork and rebase your branch to bring it en par with the master branch on the upstream, but if you apply your changes directly to master you won’t be able to do so without loosing your changes.

Right, I believe we are on the same wavelength. I used the link you provided, hit Edit, made my edit and selected “Create a new branch”. After hitting Commit Changes, it takes me to the error page.

Ok, so this time you did manage to create a new branch, but only committing changes failed?

This error 500 page you’re getting is a rather generic error, so it doesn’t really say much about what’s going on. I’ve checked the GitHub Status page and it doesn’t report any services being down right now:

https://www.githubstatus.com/

So the problem is not related to server problems. At this point, I suspect that something is not working properly on the client side, i.e. a problem with your browser or Internet connection.

I use the GitHub WebUI a lot, but not for Git operations though — I do all repository editing locally via Git, and only use the WebUI for pull requests, Issues, etc.

If the problem is due to internet connection failures, or some browser problems, etc., you end up needing to refresh the page (as mentioned in the error page), which puts you at risk of loosing your contents changes.

My advise would be to do one operation at the time, when working in the browser — i.e. first create the branch, then edit the file and commit changes, and then create a pull request. Being in control of each step is better if these errors are frequent.

Also, I suggest you do all editing work in an actual editor, and only when the changed file is ready you then click on Edit, paste your changed contents over the originals (select all and paste over), so that the operation doesn’t take too long — the problem might be related to timeout. At least, if you get the 500 error page, you don’t loose your changes, which are still in the editor.

I also strongly advice against navigating back in history during these delicate operations, since cookies play an important role in account related operations, and using the “back/forward” buttons in the browser is not the same as navigating naturally through GH WebUI, for they might revert some page-related status which GH needs to track your current user session. Also, having multiple GH pages at once might lead to problems, especially if more than on browser tab points at the same page.

Also, check that you don’t have some browser extension that might interfere with the process (e.g. ads or pop-ups blockers) or some invasive anti-virus or anti-malware tool that monitors Internet navigation and (for example) prevents sending user data over the Internet, or interferes in some other way with your session account.

Basically, anything that could interfere with your browser session (anonymizing tools, proxies, whatever)

I didn’t create a new branch, because that button says it does it for you, but it fails?

Doesn’t seem like a browser or internet issue, since I tried different browsers and devices, and even put my iPhone on LTE rather than Wifi to try different internet connections.

I’ll try creating a branch without using that button.

Well creating a branch and making changes didn’t work either, same error :frowning:

Clearing cookies did not change anything either.

Then you might have to wait for some GH staff members to check what’s happening on their servers, maybe from their logs they’d be able to provide more details on what’s happening.

I do remember though that in the past years, during the Summer heat, we did experience all sorts of Internet related problems, due to overheating of electronic devices. I myself had to replace a monitor that “fried” in front my eyes, and a few other devices that overheated and were damaged.

I’m just surprised that the error is always a generic one, usually server-side problems are able to provide specific details of what happens. So I tend to still think that the problem is either on your side (PC or router) or somewhere along the network line — either a time out, or data being corrupted in the process.

Why don’t you try doing the same operations using Git command line, or GitHub Desktop? This would allow to narrow down the problem (if it works, then there problem is either with the browser(s) or the WebUI).

1 Like

Thanks for the continued help…I’ll give that a shot tomorrow. Interestingly, I tried creating a repo from scratch and was able to add files and edit them without issues.

That’s strange indeed. These are repository operations too.

I checked the repository, to see if it contained code owner rules which might be blocking code changes, but it didn’t. I only noticed that it contains Git modules, but this should interfere with these operations.

Let me now how testing with Git/GitHub Desktop went!

Pushing the change from GitHub Desktop was successful, with no issues, and I was able to view the edit on GitHub Web! I guess I’ll just go that route from here on out.

Also - Thanks again for the help!

1 Like