Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Issues using with a Google Apps account

Open
  • Is something wrong?
#9 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
gcp
Domain
authentication, backend

Research direction

Start by reproducing the admin-link failures with each Google account setting, then inspect the custom site.yaml and the settings or resource entries described in App Engine Data Viewer. Done means the admin page works for Google Apps accounts without the reported server error or 404.

Written by the indexing model from the issue text.

Description

Note: recreated it as I accidentally closed when adding a comment

Firstly - thanks for this, it was exactly what I was looking for!

I am trying to use it with my google apps gae account.
Firstly, I when I created the application on gae I had this set:

If your application uses authentication, anyone with a valid Google Account may sign in. (This includes all Gmail Accounts, but does not include accounts on any Google Apps domains.)

So clicking on the admin page asked me for a Google account, which I wasn't using. Anyway, I then added a google account as a collaborator, and then tried to login to the admin link from DryDrop using this account, which results in:

'Error: Server Error

The server encountered an error and could not complete your request.
If the problem persists, please report your problem and mention this error message and the query that caused it.'

So I recreated the app, and selected this option:

"If your application uses authentication, only members of this Google Apps domain may sign in. If your organization uses Google Apps, use this option to create an application (e.g. an HR tracking tool) that is only accessible to accounts on your Google Apps domain. This option cannot be changed once it has been set."

However, now when I click on the admin link for the Google Apps version of DryDrop that I have uploaded, I get:

"404 - Unable to process the page

I'm sorry for inconvenience

What you can do now?

Remember, what have you done before it broke?

You have probably syntax error in your custom site.yaml. Please double check it and possibly fix it. Or remove your custom site.yaml altogether.

Normally you would clear cached resources from admin section, but at this point, the admin section is probably unavailable.
Go to https://appengine.google.com, select this GAE project and navigate to "Data Viewer". Switch to Resource entity and delete all cached resources. Then try to refresh this page again."

In the Datastore Viewer, I couldn't figure out how to navigate to resources, (possibly because there are none of that type?), however with the 'by kind:' selector set to settings (the only option), I see one entry, which lists

"id=1 site.yaml wfrict.appspot.com http://github.com/darwin/drydrop/raw/master/tutorial 1"

Thanks for creating this, and hopefully this will be comprehensive enough to sort this out :)

Pre-edit: Worth noting that by manually editing the site.yaml and entering my github address, the site does display properly - however the admin section still doesn't work.

Dominant language
Python
Stars
221
Forks
29
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from binaryage/drydrop

All issues in binaryage/drydrop

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.