# Correct charset in nginx

**URL:** <https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964>\
**Category:** Help with Setup/Upgrade\
**Created:** [April 23, 2021, 7:11pm UTC](https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964 "2021-04-23T19:11:47Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![sbayeta](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/s/22d042/32.png) [@sbayeta](https://discourse.mailinabox.email/u/sbayeta)\
**Post date:** [April 23, 2021, 7:11pm UTC](https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964/1 "2021-04-23T19:11:48Z")

</div>

Hi guys, I’m a new user of Mail-in-a-Box (started this morning) and I’m already loving it!

I changed the landing page to show my contact information, but the page seems to be served using the wrong charset. I’m also new to nginx so I googled it and found that I should add `charset utf-8;` in the `server {}` declaration of my NGINX configuration file.

I went ahead to do this but found a warning in the config file that says I should not modify it because MiaB will overwrite it.

Can anyone tell me if this is something I can modify in any way? It says in the same note to not ask for help regarding this config, but maybe utf-8 should be a standard setting? My native language (and my landing page language) is Spanish, and now “Consultoría” is served as “Consultoría”.

Thanks for any help no this matter.

Santiago

---

<div class="post-metadata">

**Author:** ![openletter](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/o/f1d935/32.png) [@openletter](https://discourse.mailinabox.email/u/openletter)\
**Post date:** [April 23, 2021, 7:32pm UTC](https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964/2 "2021-04-23T19:32:51Z")

</div>

Usually creating new files is not overwritten by MiaB.

In most nginx installs, you can add a configuration file to `/etc/nginx/conf.d/` and that will work for anything universal to the nginx `http` block, though not an individual server block.

So I _think_ you can just create `/etc/nginx/conf.d/charset.conf` and just put in the file `charset utf-8;` to get this to work for you.

---

<div class="post-metadata">

**Author:** ![sbayeta](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/s/22d042/32.png) [@sbayeta](https://discourse.mailinabox.email/u/sbayeta)\
**Post date:** [April 23, 2021, 9:55pm UTC](https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964/3 "2021-04-23T21:55:45Z")

</div>

Thanks! I’ll try that as soon as I get a new VPS running. I just found out that Digitalocean now blocks port 25 for new instances, so I can not host my MiaB there.

Cheers!  
Santiago

---

<div class="post-metadata">

**Author:** ![openletter](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/o/f1d935/32.png) [@openletter](https://discourse.mailinabox.email/u/openletter)\
**Post date:** [April 24, 2021, 6:30pm UTC](https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964/4 "2021-04-24T18:30:31Z")

</div>

Try sending support a ticket.

---

<div class="post-metadata">

**Author:** ![sbayeta](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/s/22d042/32.png) [@sbayeta](https://discourse.mailinabox.email/u/sbayeta)\
**Post date:** [April 26, 2021, 5:28pm UTC](https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964/5 "2021-04-26T17:28:25Z")

</div>

I did, and unfortunately the informed me that they don’t open this port for new instances. They suggested some workarounds which I think would take a lot of my time to implement. I told them that I just want to make it work without giving it much time, and that I would look for a different provider if they didn’t open the port. Then they suggested the same workarounds and told me they cannot open the port at this time.

So I just left and now I’m looking for a different provider. Is Linode guaranteed to open this port? Do you have any suggestion regarding other vendors?

Thanks!  
Santiago

---

<div class="post-metadata">

**Author:** ![openletter](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/o/f1d935/32.png) [@openletter](https://discourse.mailinabox.email/u/openletter)\
**Post date:** [April 26, 2021, 5:39pm UTC](https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964/6 "2021-04-26T17:39:31Z")

</div>

Does this policy apply across all data centers?

---

<div class="post-metadata">

**Author:** ![sbayeta](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/s/22d042/32.png) [@sbayeta](https://discourse.mailinabox.email/u/sbayeta)\
**Post date:** [April 26, 2021, 7:51pm UTC](https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964/7 "2021-04-26T19:51:55Z")

</div>

They really didn’t say. Here’s their last response:

> Unfortunately, each account is evaluated as its own entity. We are very sorry, but we are unable to remove the restrictions on SMTP on your account at this point in time.
> 
> We realize this is inconvenient, but many customers in your position move their mail activities to a third party service such as SendGrid or similar, which will process mail separately from their droplet.
> 
> In terms of a workaround, here are a few alternatives:
> 
> 1. Utilize a 3rd party mail API, we don’t officially affiliate with anyone but one option is Sendgrid: [Authentication | Twilio](https://sendgrid.com/docs/API_Reference/index.html)
> 
> 2. Utilize a non-default SMTP port like 2525. Sendgrid also offers this: [How to Send an SMTP Email | Twilio](https://sendgrid.com/docs/API_Reference/SMTP_API/getting_started_smtp.html)
> 
> Please feel free to reach out to us if you have any additional queries. We’re always here for you!

Really crazy policy in my opinion. I offered to update my droplet from $5 to $15 (I can use it for other projects), but it didn’t help. Maybe they should just monitor activity in suspicious accounts, instead of blocking it for everyone.

---

<div class="post-metadata">

**Author:** ![openletter](https://discourse.mailinabox.email/letter_avatar_proxy/v4/letter/o/f1d935/32.png) [@openletter](https://discourse.mailinabox.email/u/openletter)\
**Post date:** [April 26, 2021, 9:34pm UTC](https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964/8 "2021-04-26T21:34:54Z")

</div>

I’ve been using Vultr without issue, though some report they have to request port 25 to be opened.

---

<div class="post-metadata">

**Author:** ![system](https://discourse.mailinabox.email/uploads/default/original/2X/4/4d0933d13c456b7e57f296aa6cc344525b6f0c70.png) [@system](https://discourse.mailinabox.email/u/system)\
**Post date:** [May 3, 2021, 9:35pm UTC](https://discourse.mailinabox.email/t/correct-charset-in-nginx/7964/9 "2021-05-03T21:35:42Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.