I have a domain that is run through Cloudflare. I want to receive custom emails for my domain such as hi#domain.com. I want those emails to be forwarded to my personal gmail address.
I set up Mailgun with my domain, and it verified the MX, TXT, and CNAME records are set up correctly at Cloudflare. I set up a route on Mailgun to forward any mail sent to my domain to my personal gmail account. However, I am still not receiving email send to hi#domain.com.
I have set up mailgun using the recommended domain mg.domain.com
I have had a similar issue that turned out to be related to the Spam Experts system, called Professional Spam Filter in Cpanel. Within that subsystem under Incoming there is an Edit Route. That needed to be changed from the domain name to the Server name (name of the host server).
I tested it on two different domains and it worked instantly.
I'm trying to setup my domain to receive emails through Mailgun and Cloudflare, and i think i'm really closest but can't make it work.
In Mailgun, i've all DNS verified:
I think the problem is in Cloudflare, configuring the subdomain (that Mailgun suggest me to create mg.mydomain.com)
I have not got any record related with the subdomain (mg.mydomain.com). Is any change i'm something?
Also, I already setup a Route in mailgun to redirect incoming emails to my email address.
Thanks in advance!
I found the answer here:
https://community.cloudflare.com/t/setting-mx-records-for-a-subdomain/4942/2
What you need to do is:
On Mailgun:
Setup a domain for your incoming email (e.g.: foo.example.com)
On Cloudflare:
Go to DNS
Add an A record for your subdomain (foo.example.com)
Add an MX record. For the first field (name), put: foo.
When you click 'click to configure', it will open a dialog box where you can put the values for mxa.mailgun.org
Repeat for mxb.mailgun.org
For the CNAME record, you just need to make sure that the status is configured as 'DNS Only' (the little cloud on the right is grey)
I'll preface this by saying I'm very new to working with webservers, so hopefully this is not a drop-dead simple issue - but I've yet to find a solution for creating an email account for my domain.
I was trying to create a new email address under my webserver domain due to purchasing an SSL certificate. I'm using www.ssls.com to provide the cert, and the final step is to provide an email account for the approver email to receive the cert. However, I can only choose to send the cert to a list of generic emails on my domain, such as admin#my_domain_name.com. This seemed like a straightforward issue, but have yet to find a solution to create a new user account/email to receive the certificate.
I tried using the Bitnami document to add Webmin to my webserver to manage emails, but I seem to be getting issues accessing the files under etc/webmin/apache due to permission issues, even though I'm logging into as the root user.
Am I missing something extremely simple in this process? It seems like setting up an email on the domain should be a relatively straightforward process, but I've yet to find a way to do this. The webserver is hosted on Azure using the Bitnami LAMP stack and Apache.
Any advice would be greatly appreciated.
Bitnami developer here.
Your domain provider probably gave you an email address like admin#yoursite.com. You should check with them.
You could also try to enter to your provider admin panel and see if you can configure your email.
I'm trying to set a web service that needs the user's Google Latitude info, so I'm using Google OAuth to get the user authorization stuff.
However, when trying to set the redirection URI in the Google APIs Console for a web application client ID I get a message error if I try to set it to 'http://PUBLIC_IP/'.
I need to test it with non local users (thus localhost can't be used), so I would like to know if having a web domain is mandatory in order to use Google's OAuth. If not, how can I solve this issue?
This is not currently supported. I filed a feature request and will update on progress.
Update: Essential app verification activities have continued to make support of IP address-based apps unlikely. These verification activities are necessary to provide protections against abuse of user accounts. In addition, the cost of setting up dedicated domains has been reduced significantly since this feature was requested. Please read other responses here about possible options.
You can use xip.io to work around it.
For example: '192.168.0.50.xip.io:3000' will resolve to '192.168.0.50:3000'
I ran into this issue too and so I entered a URL with a .com extension and also entered it into my /etc/hosts file. Works like a charm.
It totally sucks that my entire app now has to be developed on an apparently 'live' domain though.
I used my public hostname. It helps if you have a static IP address. I used http://www.displaymyhostname.com/ to get my hostname. I plugged it straight into the Authorized JavaScript origins field when I created a new Web Application Client ID.
P.S. My hostname looked something like this: 111.111.111.111.static.exetel.com.au
You can use a dynamic DNS. I used ddns.net which offers a free solution. Basically, you enter your FQDN as this: yourcompany.ddns.net as your domain. When looked up for an IP address, the .net domain points to ddns; when ddns.net is looked up, it looks up in its database for your company, returns the IP. So mine looks like this: https://wigwam.ddns.net and everything works fine. You don't need to buy a domain, you can substitute your known IP, and Google is happy with that.
Your IP must be static, of course.
Yes, as of now you still need to have a domain name to use Google OAuth in your application. If you have a static public IP and don't want to buy a domain name, you could use a free subdomain from FreeDNS to link to your public IP. Seemed to work well enough for me with a Django app.
Echoing what Breno said in response to his earlier comment:
Apologies for the lack of updates here. Essential app verification activities have continued to make support of IP address-based apps unlikely. These verification activities are necessary to provide protections against abuse of user accounts. In addition, the cost of setting up dedicated domains has been reduced significantly since this feature was requested. Please read other responses here about possible options.
You can read more about Google's app verification requirements [1] and Google's policies requiring secure handling of data [2].
[1] https://support.google.com/cloud/answer/9110914?hl=en
[2] https://developers.google.com/identity/protocols/oauth2/policies#secure-response-handling.
xip.io is not working anymore as an alternative you can use nip.io the same way for example:
10.0.0.1.nip.io:8000 will resolve to 10.0.0.1:8000
It seems like xip.io is down, but there are alternatives such as sslip.io and nip.io. However, I couldn't get either of these to work.
I ended up hosting the main file server on the main machine, and ran said server on a 192.168.1.xx IP address. I then ran servers on each of the test machines (including a second server on the main machine), all of which were on the localhost address. Any requests that the localhost servers received were then passed off to the 192.168.1.xx server, which allowed testing on all of the devices.
This should also work with public facing IP addresses.
I have a list of sites running on the same server, so they all share the same IP address. a facebook app was created in order to have login functionality on the sites, but as I see, the app needs one and only domain (for security reasons...) that is enabled to use the login process.
Is there a way to identify remote sites with IP instead of one domain name?
Thanks!
No, you must use a domain name, you can enter multiple domain names though, or run the logins through login.yoursites.com or something like that