Can't install WordPress on port other than 80

[anonymized_13628566]

Trying to do local development (using Docker) on port 8080.

Dock images: php-fpm, nginx, mysql.
Using a fresh install, with a blank database and wp-config.php removed,
going to ​http://localhost:8080/ forwards to ​http://localhost/ which is apparently not accessible.

Please remove this and let me install WordPress on any port.
To verify this is a WordPress problem and not nginx related, consider the following:

​http://localhost:8080/license.txt does show up perfectly

​http://localhost:8080/test.php
A testscript containing nothing more than <?php phpinfo(); also works as expected:

​http://localhost:8080/ which should forward me to setup routine, does not work, instead it does redirect:

Content-Type: text/html; charset=UTF-8
Date: Thu, 15 Aug 2019 14:10:27 GMT
Location: ​http://localhost/
Server: nginx/1.17.2
X-Powered-By: PHP/7.3.8
X-Redirect-By: WordPress

I don't know how other people deal with this major issue, this is a kinda wtf moment for me.

[anonymized_13628566]

It seems WordPress is comparing $_SERVER['HTTP_HOST'] to $_SERVER['SERVER_NAME'] and $_SERVER['SERVER_PORT'].

I have not put much thinking into it yet, but doesn't this result in pretty much conflicts when WP is setup on multiple nodes behind a reverse proxy?

Btw how to delete the ticket..

[anonymized_13628566]

People, there is no DELETE option on tickets?!

Consider this a GDPR request:
Please fully delete my ticket from your system.
Do not set it to some pseudo "deleted hurr durr" status but do a real delete.

[anonymized_13628566]

There is another bug:

When I go to https://core.trac.wordpress.org/my-tickets

My tickets are not shown. So sad!

[garrett-eclipse]

Hi @DanFromGermany

Your tickets won't show on that report as they're all closed and that report only lists active tickets. For a full listing of all your tickets here's a custom query;
https://core.trac.wordpress.org/query?reporter=DanFromGermany

As to ticket deletion that feature isn't available standardly as trac is an archival record for the open source project. Usually only malicious tickets (spam, pentesting, exploited) are removed.
*Concerning GDPR the archival record (Trac) is addressed in section f of article 6 which states "processing is necessary for the purposes of the legitimate interests pursued by the controller".
Reference - ​http://www.privacy-regulation.eu/en/article-6-lawfulness-of-processing-GDPR.htm
*This is also covered in the WP.org Privacy Policy - ​https://wordpress.org/about/privacy/
"WordPress.org will not delete personal data from logs or records necessary to the operation, development, or archives of the WordPress open source project."
"When deletion is requested or otherwise required, we will anonymise the data of data subjects and/or remove their information from publicly accessible sites if the deletion of data would break essential systems or damage the logs or records necessary to the operation, development, or archival records of the WordPress open source project."
*That being said you can contact dpo [at] wordcamp.org for a more official statement as I'm just a volunteer, or you can use the Data Erasure Request form although I don't believe it would delete any tickets as they are seen as an archival record.
Data Erasure Request form - ​https://wordpress.org/about/privacy/data-erasure-request/

I hope that answers your questions
All the best

[anonymized_13628566]

I don't understand why you don't simply but an ANONYMIZE button then instead of a DELETE button.
Now I have to write emails and stuff.

Thinking how big wordpress is, you don't even have a delete button lol

Thanks tho for your answering...

[anonymized_13628566]

Dude "archival" reason does not counter the possibility to delete stuff from an archieve. It's plain annoying, not more, not less.

"processing is necessary for the purposes of the legitimate interests pursued by the controller"

"legitimate interests" is a legal loophole, as both definitions are free to your own creativity. There is no legit reason you keep my ticket, EVERY software developer knows that. Nothing will stop working when you delete my information. It's bullshit for companies to be legitly lazy and let users struggle.

[garrett-eclipse]

Hi @DanFromGermany, as a volunteer I can only really echo things I'd heard. For official response/actions there your best bet is dpo [at] wordcamp.org.

As to the anonymize button if you'd like to request a new feature on Trac you can open a ticket via Meta Trac where that's handled.
Meta Trac - ​https://meta.trac.wordpress.org/

[anonymized_17446112]

Thanks again for your reply Garrett, I appreciate your time and effort.

My right to have personal data removed is not negotiable.
I just want my name "DanFromGermany" removed in all comments here.
Also comment #6. The sum of significant bits in this context make up "identifiable data", which is one step from beeing anonymous.
Please respect my privacy.
I am fine if you again block my account, as long as you remove any data potentially identifying me.

Thanks for time and effort.

[garrett-eclipse]

No worries @danfromgermany2

Concerning data requests your best bet will be dpo [at] wordcamp.org. That being said while your account can be scrubbed of data the username will be left alone and most likely it's associations to comments due to security and system integrity.

With all of the logging systems for development of WordPress; Slack, Trac, GitHub, IRC, wp.org/support. You have control over your profile and what information is publicly displayed. And can make an erasure request if you need that information removed. In many cases like the Plugin repo and Trac a full removal isn’t possible as it’s a security risk to remove a username and allow another malicious dev to take over their plugins or tickets, in these cases the username is exempt from erasure but the rest of the profile can be removed or anonymized.

Disclaimer: I’m not a lawyer and don’t work for the WP foundation so this is my personal understanding.