I have recently migrated from GSuite (+ hosting) to Dreamhost. I transferred the hosting from GSuite and stopped email as well.
My webmail on Dreamhost is however not reachable (404 error) while for another website I host on Dreamhost it is working properly.
I am guessing there is a setting in G-Suite I need to turn off but I have no idea what that might be.
Anybody had a similar issue?
Related
I am developing an application that needs to be delivered as following:
PWA application server(Host app/IIS) is installed in the local network
PWA should support offline
Domain SSL not possible on the server as it's not a domain
Un attended installation
No configuration should be forced on the client machine, to change chrome settings etc.
I have tried:
Running from VS, Only works on same machine by design
Published to IIS and tried, works ok on the same machine. Offline does not work on mobile
Self sign SSL is not helping, Offline does not work
One option I found is to host it on our server on the internet, after installation access data from intranet server. Not yet tried this.
Looks like it is impossible to deploy PWA as intranet application with self-sign SSL. Am I missing something ?
Is there a way to automate deployment of PWA with self-sign that supports offline working?
I have a GCP project. Then I gave permission to a user A with email A#email. They connected it to Firebase and developed a project there with hosting enabled and verified. Then another user B came and I switched the ownership of the project to them and removed A from this. After ownership change, the hosting verification was re-triggered (as expected). However, since 1 week it only shows
I tried searching for other people who had such an issue and nothing came about. I even wrote a bug report but for more than a week nobody has reached out to me and I am worried because the grace period is 1 month and I my project could go down. Have you heard of similar problems?
Edit from comment:
I can confirm that the error comes in Chrome and incognito (version: 80.0.3987.163 (Official Build) (32-bit)) and in Firefox and incognito (version: 72.0.2 (64-bit)). Opening the console gives error 503 for URLs https://clients6.google.com/siteVerification/v1/webResource?verificationMethod=DNS_TXT&alt=json&key= and https://clients6.google.com/siteVerification/v1/token.
The issue was due to my company's license agreement with Google and the way Firebase Hosting is made. More details below.
Strangely enough, using GCP and Firebase require a GCP license. With this license you can do everything from adding/changing/modifing collections/projects. However, the functionality to 'Verify' your hosting site goes through the Google Console which is not included in the license.
Encountered this same thing. The problem turned out that I was using a Google Workspace account that did not have "Google Search Console" enabled for the domain I was logged in on.
To remedy, I had to login to my Workspace Admin, and go turn it on as shown below.
I'm using MAMP Pro v3.5 for local development. I have multiple dev sites running successfully without a problem. When it came to testing a site on my phone, I used the out of the both 'Name resolution [x] via Xip.io (LAN only)' option under the hosts tab. The first host I turned that on with was fine and worked very well (using address like www.siteone.dev.192.168.0.10.xip.io).
The problem came though when I attempted to setup a second dev site on Xip.io using the above method. Now using a different URL (using address like www.sitetwo.dev.192.168.0.10.xip.io) for the second dev site, no matter what I try, I get the first host that was setup rather than the expected second.
Is this a bug with MAMP Pro, or it's just not capable. I've tried turning off the 1st host I setup with MAMP Pro, but it still shows up as the site that is getting served under the second xip.io address I setup.
Would really appreciate one of the MAMP people to respond and confirm if this is expected behaviour. An extended Google search didn't turn up anything.
Thanks
Brendan
We have to migrate a lot of email from an IMAP server to Gmail in Google Apps. Google Apps have a migration tool, but it works only with a server with a valid SSL certificate.
We wouldn't want to do a manual import... someone have a suggestion?
Try using GAMME. It should do SSL w/o a valid cert.
So I've been running CF9 on Linux for a while and using CFMail to send email through a client's Exchange 2010 server for quite a while.
We're attempting to migrate to CF10 on Win2008, IIS7.5. Everything is set and ready to go except I can't get CF10 to verify the mail connection? I've got both mail settings (CF9 and CF10) set the exact same way and can view them open side by side and verify they're identical. However, while the CF9 verifies successfully the CF10 system fails??
I tried sending through CFMail tags while specifying the server credentials and see this in the CF10 log:
"javax.mail.AuthenticationFailedException: No authentication mechansims supported by both server and client"
What does this mean? I know my authentication credentials are correct because I'm able to connect in CF9.
I've turned off all firewalls and still nothing. So, I then tried installing CF10 on my Mac laptop. It, too, will not verify the mail connection!
Is there a known problem with CF10 connecting to an Exchange mail server?
Any ideas?
I "solved" this.
I could find little online and received no comments to this thread. No combination of settings I tried would work and I have no access to the client's mail server. The person who runs that server couldn't run a lemonade stand so no help there.
Then I stumbled across this page. Nothing to do with ColdFusion but seemed like a similar issue.
Recent changes in the JavaMail API has changed certain authentication
defaults and sometimes will create an authentication error with some
Exchange Server environments dependent on the configuration.
I'd never put much thought into CFMail because it was always drop dead simple and simply worked. Focusing on this link's Resolution 2 (ie replace the mail.jar with an older version). I wondered if CF used JavaMail and if I could downgrade CFMail? I cracked open CF's mail.jar file and found that CFMail does, indeed, use the JavaMail API. So, I then checked the ColdFusion docs to see if any new features were added to CFMail between CF9 and CF10. None.
So, I swapped out the mail.jar file from my CF9 install to CF10 and restarted. Boom! Everything worked immediately. As far as I can tell I've had no compatibility issues to report.
Swapping the mail.jar did not work for me. However, adding the following to JVM arguments
-Djava.net.preferIPv4Stack=true
worked for me. Please refer to the following article
Java Mail mystery - SMTP blocked?
posted by another user