# Local incorrectly adds port number when logging into wp-admin of a site

**URL:** <https://community.localwp.com/t/local-incorrectly-adds-port-number-when-logging-into-wp-admin-of-a-site/25327>\
**Category:** Bugs\
**Tags:** ssl, wp-admin\
**Created:** [April 23, 2021, 9:24am UTC](https://community.localwp.com/t/local-incorrectly-adds-port-number-when-logging-into-wp-admin-of-a-site/25327 "2021-04-23T09:24:27Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![ben.turner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/ben.turner/32/5366_2.png) [@ben.turner](https://community.localwp.com/u/ben.turner)\
**Post date:** [July 27, 2021, 7:05pm UTC](https://community.localwp.com/t/local-incorrectly-adds-port-number-when-logging-into-wp-admin-of-a-site/25327/18 "2021-07-27T19:05:36Z")

</div>

Haha! :larry_heart: Gotcha, I just wanted to make sure I wasn’t missing something 😃

Thanks for passing along that site, it was really helpful to see an example and as a result, I think I have distilled the steps down for a reliable reproduction:

1. Create a new site in local

2. Trust the SSL cert for the site

3. Open a site shell and update the url within the DB to use the secure version of the url

4. Try to log into the WP-admin when the url _does not_ have a trailing slash. So for example, using the above url, navigate to:

Since this is such an odd issue, I recorded my QA session. Note that an Nginx site will handle the redirect correctly, but the Apache site will not:

- [Screen Recording 2021-07-27...](https://i.getf.ly/L1uB0m0O)

I’ve created a bug within our internal bug tracker program, but I don’t have an ETA for when it will be fixed. As a workaround, I imagine you might be able to add an apache redirect at the site level and then restart the site.

---

_[View the full topic](https://community.localwp.com/t/local-incorrectly-adds-port-number-when-logging-into-wp-admin-of-a-site/25327)._