I'm trying to deploy my meteor app to Galaxy to a new subdomain, let's call it xxx.mydomain.com. I'm getting the following console output:
Talking to Galaxy servers at https://galaxy.meteor.com
Error deploying application: This domain has already been used on Galaxy. [xxx.mydomain.com]
I don't have an app with this domain, my guess is someone else is using it? How do I fix this? I tried looking up this error but nothing shows up on Google and Meteor docs don't seem to help either.
Related
I have a multi-page web application written in Flutter which uploaded on Firebase hosting . All the pages work fine but half of the homepage is grey. Photo attached. Really appreciate for help.
Also, I'm getting this error when I run: flutter run -d chrome --release
Oops; flutter has exited unexpectedly: "ProcessException: The application has failed to start because its side-by-side configuration is incorrect. Please see the application event
log or use the command-line sxstrace.exe tool for more detail.
Command: C:\Users\abc\AppData\Local\Google\Chrome\Application\chrome.exe --user-data-dir=C:\Users\abc\AppData\Local\Temp\flutter_tools.2b59d482\flutter_tools_chrome_device.4fad7966 --remote-debugging-port=2576 --disable-background-timer-throttling --disable-extensions --disable-popup-blocking --bwsi --no-first-run --no-default-browser-check
--disable-default-apps --disable-translate http://localhost:11541".
I have also faced same issue while host web app in firebase.
the issue is not in firebase host. the issue is in your code. your code will completely work in debug mode. but not in released mode.
check every warning in logs.
it is mostly happen because of wrong use of expanded or flexible widget
So I just got into meteor like a month ago, and I just finished my first website after about 2 weeks. Its a social media website kinda like twitter. I also downloaded accounts-ui and accounts-password packages, and I implemented them in the website pretty loosely. But heres the thing, I wanna deploy the website to galaxy using the subdomain .meteorapp.com, and it just doesn't seem to work. I keep getting the same error in the logs which is: "Error: MONGO_URL must be set in environment". I looked it up, and I just dont know what to do. from what I read online you need to make a settings.json file, then add this code:
"galaxy.meteor.com": {
"env": {
"ROOT_URL": "http://blueslipgang.meteorapp.com/",
"DEPLOY_HOSTNAME":"galaxy.meteor.com"
"MONGO_URL":"mongodb://127.0.0.1:3001/meteor"
}
}
so thats what I did, and i added this file to the client file, the server file, and even inside no file. I just cant seem to get the website to deploy. I really wanna deploy this website so me and my friend's can use it, but its just not deploying.
so what am I doing wrong, and what do I need to do to fix it. Any help would be really, really appreciated, I worked pretty hard to make this app, and it would really suck if I cant even deploy it.
Thank you
Galaxy doesn't provide a MongoDB service, so you will need to sign up for a MongoDB account (Atlas has a free tier) and use that. Setting the MONGO_URL to localhost/127.0.0.1 will throw an error on launch.
Also, to use the settings.json when deploying, you will need to make sure you have the --settings flag set in your deploy command:
DEPLOY_HOSTNAME=galaxy.meteor.com meteor deploy [hostname] --settings settings.json
Also have a read through the official galaxy guide
If you have ongoing problems, I suggest posting on the Meteor forums and the community can help step by step with each issue you run into
I made some recent updates to my Meteor App, most notably updating to Meteor 1.7. Since then Galaxy's deploy fails, errors:
Talking to Galaxy servers at https://eu-west-1.galaxy.meteor.com
Preparing to deploy your app...
Uploaded app bundle to upgrade kampino.afkl.com.de to version 38.
Galaxy is building the app into a native image.
Building app image...
Deploying app...
(This message is different than before...)
In the versions tab of Galaxy it says: Deploy Failed
Any idea?
When I checkout the older version everything works normal again.
I suppose it is about Meteor 1.7 but didn't find any issue or question on it.
Regards
Just in case anyone has the same problem:
It seems like in the new Galaxy Deployment some special characters my password was containing don't go anymore. Error log:
Error: Password contains an illegal unescaped character
I'm trying out Polymer web components for the first time and everything is working perfectly fine using Brackets Live Preview.
But when I try to deploy the app using Firebase hosting I get a READ ERROR.
READ ERROR - Could not read directory. Remove symbolic links / shortcuts and try again.
I updated firebase-tools but still get the same error.
I've spent so many hours going through tech forums hoping I'd find somebody having the same issue but unsuccessful.
Any information regarding my inquiry is much appreciated.
Your app's directory contains a shortcut or a symbolic link. You need to replace that with the actual content before firebase-tools can upload the site. Once you've removed the shortcut firebase deploy should work as expected
On localhost, the app works just fine.
On EC2, the app runs behind nginx. It loads into the browser, but nothing shows up. The browser console displays an Error
TypeError: 'undefined' is not an object (evaluating 'Package["service-configuration"].ServiceConfiguration')
I have no idea how to tackle this problem. Any help appreciated.
EDIT
NGINX is not the problem. The same behavior if I access meteor server directly.
Running "meteor add service-configuration" does fix the above mentioned error, but the absence of the error does not fix the observed behavior, that the app does not render on EC2 whereas it does render when started on localhost. (The error message was the only visible difference between EC2 and localhost. So I suspected that would be the cause. Now that hypothesis must be wrong.) So the problem still persists.
Problem Solved. The Lesson:
Meteor has a debug mode and a production mode. The two may behave differently. On localhost, meteor runs in debug mode per default. On deploy to meteor.com or per mup, the default is production mode. To run meteor in production mode on localhost, run meteor --production.
It looks like you're trying to access the service-configuration configs on your browser.
These are not available client side. This also affects your localhost app but it doesn't break your app (doesn't give you a blank page) because meteor is in debug mode.
In debug mode Meteor files are not concatenated so an error like this would go unnoticed, even if it is thrown on your js console. In production mode the error would halt the rest of your script (since everything is concatenated into a single file)
You need to ensure the code that is doing this only runs on the server side. In general it's not a good idea to have access to the service configuration data on the client side.
Looks like Arunoda and crew are adding a buildOptions.debug setting to the next version of MUP, which should allow you to deploy via MUP and have it act like it's running on localhost. See Arunoda's answer to a related question and (at least for now) documentation for the development version of MUP.