It is hosted on azure, so the domain is https://our-subdomain.azurewebsites.net.
The only thing on the same subdomain is parse server.
We are running as express middleware with parse server on the same url and port:
var express = require("express");
var ParseServer = require("parse-server").ParseServer;
var ParseDashboard = require("parse-dashboard");
var MyFirebaseAuthAdapter = require("./myFirebaseAuthAdapter");
var databaseUri = process.env.DATABASE_URI || process.env.MONGODB_URI;
if (!databaseUri) {
console.log("DATABASE_URI not specified, falling back to localhost.");
}
var serverUrl = process.env.SERVER_URL || "http://localhost:1337/parse";
var serverConfig = {
databaseURI: databaseUri || "mongodb://localhost:27017/dev",
cloud: process.env.CLOUD_CODE_MAIN || __dirname + "/cloud/main.js",
appId: process.env.APP_ID || "myAppId",
masterKey: process.env.MASTER_KEY || "123",
serverURL: serverUrl,
appName: process.env.APP_NAME || "mysite.org",
auth: { myauth: MyFirebaseAuthAdapter },
allowClientClassCreation: false,
};
var api = new ParseServer(serverConfig);
// Client-keys like the javascript key or the .NET key are not necessary with parse-server
// If you wish you require them, you can set them as options in the initialization above:
// javascriptKey, restAPIKey, dotNetKey, clientKey
var dashboard = new ParseDashboard({
apps: [
{
appId: serverConfig.appId,
serverURL: serverConfig.serverURL,
masterKey: serverConfig.masterKey,
appName: serverConfig.appName,
production: serverConfig.serverURL.includes("production"),
},
],
trustProxy: 1,
users: [
{
user: serverConfig.appId,
pass: serverConfig.masterKey,
},
],
});
var app = express();
// Serve the Parse API on the /parse URL prefix
var mountPath = process.env.PARSE_MOUNT || "/parse";
app.use(mountPath, api);
app.use("/dashboard", dashboard);
var port = process.env.PORT || 1337;
var httpServer = require("http").createServer(app);
httpServer.listen(port, function () {
console.log("parse-server running on port " + port + ".");
});
Note that since Google flagged it, we have since turned on the setting in Azure to force https. We also correctly configured the trustProxy
setting. So it is possible it was related to one of those, but it still seems like the Google bot must have seen something in code, not just the configuration.