Ghost Admin Login Error – "There was a problem on the server"

[zareen]

Uncaught TypeError: firebase.auth is not a function: This error indicates that you’re trying to call firebase.auth() as a function, but in the Firebase modular (v9+) or compat APIs, firebase.auth (when properly initialized via side-effect imports like import ‘firebase/compat/auth’) is a namespace, and to get the auth service instance, you should call app.auth() on your initialized Firebase app instance (app).
I will correct this in your services/firebaseConfig.ts file.
Uncaught TypeError: Failed to construct ‘URL’: Invalid URL: This error means that a string being passed to the new URL() constructor is not a valid, complete URL. This often happens if the URL string is relative (e.g., “/some/path”) without a base, malformed, or simply not a URL. This is most likely occurring in services/geminiService.ts within the parseGeminiResponse function when processing URLs returned by the Gemini API, or subsequently in ResultItemCard.tsx if a malformed URL string makes it through.
I’ll make the URL parsing in parseGeminiResponse more robust to ensure that only valid, absolute HTTP/HTTPS URLs are set, or null otherwise. This should prevent invalid strings from being passed to new URL() later.

The Firebase error should now be resolved by correctly initializing the auth service in firebaseConfig.ts. The "Invalid URL" error should be mitigated by the more defensive URL parsing in geminiService.ts, ensuring that only well-formed, absolute HTTP/HTTPS URLs are passed on, or null if a valid URL cannot be confidently determined from the Gemini API's output.

[zaasmi]

The Firebase error should now be resolved by correctly initializing the auth service in firebaseConfig.ts.
The “Invalid URL” error should be mitigated by the more defensive URL parsing in geminiService.ts, ensuring that only well-formed, absolute HTTP/HTTPS URLs are passed on, or null if a valid URL cannot be confidently determined from the Gemini API’s output.

[zaasmi]

@zareen

You should ideally use the Admin SDK on server. The error you are getting might be because you’ve installed Modular SDK (v9.0.0+) which does not use the name-spaced syntax. Try installing Admin SDK (firebase-admin) and refactoring the code as shown below:

router.post('/user', async function (req, res, next){
  try {
    const newUser = await userService.addUser(req.body.email, req.body.password);
    return res.json(newUser)
  } catch (error) {
    console.log("Error : " + error);
    req.sendStatus(500).send(error);  
  }
});

const admin = require("firebase-admin");

admin.initializeApp({
  // service account
});

exports.addUser = async (email, password) => {
  return admin.auth().createUser({ email, password });
}

You cannot login user using Admin SDK (unless you are using session based auth) so after the user is created you should log the user in with signInWithEmailAndPassword() on your client application using client SDK.

[zareen]

“ServiceWorker registration skipped: Page is not served over http(s). Current protocol:” “blob:”

[zaasmi]

@zareen
The “Uncaught TypeError: firebase.auth is not a function” error typically arises when the Firebase Authentication module hasn’t been correctly imported or initialized in your JavaScript code. Here’s a breakdown of the common causes and solutions:
Missing Firebase Authentication import:
Ensure you’ve imported the getAuth function from the Firebase Authentication module.
JavaScript

import { getAuth } from "firebase/auth";

Incorrect Firebase initialization:
Verify that you have correctly initialized Firebase with your project credentials before attempting to use firebase.auth().
JavaScript

import { initializeApp } from "firebase/app";
const firebaseConfig = {
    // Your Firebase configuration
};
const app = initializeApp(firebaseConfig);
const auth = getAuth(app);

Conflicting Firebase script inclusions:
If you’re including Firebase scripts directly in your HTML, ensure there are no duplicate inclusions or conflicts.
Make sure that firebase-app.js and firebase-auth.js (or their modular equivalents) are included.
Using outdated Firebase SDK:
If you’re using an older version of the Firebase SDK, the firebase.auth() method might not be available.
Consider updating to the latest version.
Compatibility issues:
If you’ve recently updated other libraries or are encountering unusual behavior, there might be compatibility issues.
Check for known conflicts and consider using compatibility versions if necessary.
Scope or context issues:
In some cases, the firebase object might not be accessible in the scope where you’re trying to use it.
Ensure that it’s properly defined and accessible within the relevant function or module.
Asynchronous operations:
If you’re calling firebase.auth() before Firebase has fully initialized, it might result in this error.
Ensure that Firebase is initialized before attempting to use its services.
Mixing modular and namespaced syntax:
If you’re using the modular syntax (e.g., getAuth) in some parts of your code and the older namespaced syntax (e.g., firebase.auth()) in others, it can lead to conflicts.
Stick to one syntax consistently throughout your project.