I have setup 2 Droplets so far trying to get Gitlab working. I am using the Gitlab ready Ubuntu image for the auto-install when creating the droplet.
The first one was a %12,b server and gave 501 type errors, I did some research and came to the conclusion that I might need the 1gb of ram server. So I launched a new 1gb droplet with the same image and it had the same problem!
I then realized that a re-boot of the server fixed the problem so the 512mb server might of worked as well.
From this point it appeared on the surface everything was working good however when I created a new user account in Gitlab the only way to set a password is to let it email the user a password! Sounds fine except the email s would never send. It seems that the server may of not had Email setup or working by default!
As this pre-installed image was supposed to work out of the box according to all the tutorials I read, this email problem made no sense to me so I am assuming something is wrong with that prebuilt server image?
Anyone else use it to get Gitlab running and have similar issue?
The only thing I didn’t do was I did not setup a domain name on that server for Gitlab but it is supposed to work on an IP as well. I’m not sure if that would affect the emails not being sent?
Any ideas on a fix maybe?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
This question was answered by @tenbroya:
Hi guys,
I just used the OneClick Gitlab set up droplet and the only problem I ran into was also this.
The solution (for me at least) was to add an SPF record to the DNS records for the droplet.
You can do this by simply adding a TXT entry as follows:
Record type: TXT Name: your dnshostname/ipaddress Value: v=spf1 ip4:<enter the ip address of your droplet> ~all
For example. with my own domain I have an A record that aliases git.mydomain.com to my droplet’s IP address. Then I created a TXT spf record with the name of the alias as it’s name and the spf address as the droplets IP too.
With this done I am now able to get past gmails spam filter as well as my own personal mail server (uses spamassassin).
I hope this solves your issues.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.