Hi Try https://localhost/wp-login.php or.. http://localhost/wp-login.php -- Richard

Is there something listening on port 80 (check via netstat -antp)? The wp-admin request is trying port 80. You have something listening on port 9090. On 7/14/23 16:54, Bill Cunningham wrote: > > On 7/14/2023 4:09 PM, Richard Ibbotson wrote: >> Hi >> >>> I have the server edition installed and log into firefox and enter >>> https://localhost/wp-admin and I always get there's no such url. >> Try >> >> https://localhost/wp-login.php  or.. http://localhost/wp-login.php > > No that doesn't work either. > > _______________________________________________ > users mailing list -- users(a)lists.fedoraproject.org > To unsubscribe send an email to users-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue

On 7/14/2023 5:52 PM, Mark C. Allman via users wrote:

On 7/14/2023 9:15 PM, Samuel Sieb wrote: I will look at these. I might probably need a tutorial of some kind I will have to look for. Port 9090 opens fine in the Xfce 4 desktop I have installed. Maybe wordpress uses a different port. B

On 7/15/2023 3:17 PM, Samuel Sieb wrote: Perhaps PHP is not properly configured.

On Jul 15, 2023, at 15:28, Bill Cunningham <bill.cu1234(a)gmail.com&gt; wrote: I don’t mean to be rude, but you *do* have a web server installed, configured and running, don’t you? And not cockpit’s web service. Wordpress is just a collection of PHP code, it needs a web server to host it. The package (I assume) doesn’t bundle a server, most likely so you can choose between one of the popular choices. -- Jonathan Billings

On 7/15/23 14:52, Bill Cunningham wrote: It won't. You need to follow some sort of guide that explains how to set it up. Maybe there's enough info in those README files, but you'll probably have to find some external reference.

Well, I’m familiar, ‚a bit‘. 1. Before you start installing WordPress, you should check if this is what you really want. :-) WP is a beast, a prime example of bloated software and an ongoing source of security vulnerabilities. If you need a dynamic CMS, there are really better alternatives. See https://www.cms-garden.org/en. If you have no choice, proceed. 2. The way you obviously installed WP is not meant to work. Fedora Server has no graphical interface and no graphical browser with which you can view a WP page. Rather, you install Fedora Server and software like WordPress and view the content from another machine over a network connection, not localhost. Localhost also works under certain conditions, but that is then kind of "off label use“. If you want to experiment with it, then either buy a small Rasberry Pi compatible computer (see https://docs.stg.fedoraproject.org/en-US/fedora-server/server-on-sbc/refe...) or install virtualization software like VirtualBox on your desktop and then Fedora Server in it. Then you can access Fedora Server and WordPress through the internal virtual network. 3. A good fist overview provides https://fedoramagazine.org/howto-install-wordpress-fedora/ 4. The steps required are approximately as follows: a) Install Fedora Server (obviously) b) Install a database. Fedora Server supports PostgreSQL (WordPress does, too) see: https://docs.fedoraproject.org/en-US/fedora-server/services/setup-postgre... When everything works, add a database and a database user for Wordpress. c) Install a Web Server. Fedora Server Supports Apache. See https://docs.stg.fedoraproject.org/en-US/fedora-server/services/httpd-bas... d) Install the WordPress Package. It automatically installs PHP as a dependency, too. e) Edit the Wordpress configuration file: […]# vim /etc/wordpress/wp-config.php • → define( 'DB_NAME', 'xxxxx' ); • → define( 'DB_USER', 'xxxx' ); • → define( 'DB_PASSWORD', 'xxxxxxxx' ); • → define( 'DB_HOST', 'xxxx' ); Select PostgreSQL as your database and insert user name, password, etc as configured in b) f) Optionally you may adjust various parameters to your liking, e.g. the Wordpress address […]# vim /etc/httpd/conf.d/wordpress.conf (edit) ## Alias /wordpress /usr/share/wordpress ## Access wordpress via base address DocumentRoot /usr/share/wordpress # Access is only allowed via local access … But probably you should not do this with a first installation. g) Adjust the Apache Wordpress configuration file […]# vim /etc/httpd/conf.d/wordpress.conf 'Require local' → 'Require all granted‘ g) Start the Web Server […]# systemctl enable httpd […]# systemctl start httpd […]# systemctl status httpd h) On your desktop start your browser and visit the WordPress graphical configuration page <yourserver>:80/wordpress You may also wait some days until I have finished my Fedora Server documentation article. Good luck Peter -- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy(a)fedoraproject.org Timezone: CET (UTC+1) / CEST /UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast

Skimming through my text I just noted that Wordpress dropped PostgreSQL plugin in November last year (https://wordpress.org/plugins/postgresql-for-wordpress/). So you are stuck with mysql / mariadb and can’t use advanced professional db features as provided by PostgreSQL. Thanks. I need some days more because I have to rewrite the complete part about database. -- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy(a)fedoraproject.org Timezone: CET (UTC+1) / CEST /UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast

On 7/18/2023 7:16 PM, Peter Boy wrote: B

They are expected, indeed. It is incredible hard to proofread a text you have written yourself. So, some hints would be helpful. And also maybe some improvement of the wording, if my German mother tongue comes to the surface too much. Yeah, it's a kind of „off label“ use. I wrote a short text about it: https://docs.fedoraproject.org/en-US/fedora-server/usecase-gui-addon/ But to get the „real feeling“ you should use the virtualization option I described briefly. The installation of the Server Edition is one of our focal points for the next months (see https://pagure.io/fedora-server/issue/110). So I would be happy if we could communicate on that. And I'm skeptical about how happy you'll be with operating a graphical interface over a network connection. Best Peter -- Peter Boy https://fedoraproject.org/wiki/User:Pboy PBoy(a)fedoraproject.org Timezone: CET (UTC+1) / CEST /UTC+2) Fedora Server Edition Working Group member Fedora Docs team contributor and board member Java developer and enthusiast

On Fri, 2023-07-21 at 16:05 -0400, Bill Cunningham wrote: Well, if you're running servers, especially one like WordPress with so many security flaws, and also plagued with bad advice about setting things up on it on the internet, the usefulness of using SELinux is magnified. But you haven't told us if you're making this world accessible, or you're just trying it out on your LAN. The two common problem with webservers are that someone finds a way to read other files (not your web pages) on your system through it, or someone finds a way to use your webserver to write things to your file system. SELinux puts barriers in the way of that. Common bad advice on the internet is about giving file permissions that the web files are owned by the web server (instead of a different user), and are writable by other users. This includes the data that things like WordPress use to create their output. Which should be stored where *only* the WordPress application can access them. You do not want them in the middle of the web server's directory tree, where someone can directly access them bypassing the handling of WordPress. WordPress is a handler. A user requests pages with a URL like www.example.com/something/thispage through your webserver, the handler looks at the "/something/thispage" part of the request and creates an output page from data it has stored elsewhere, and it sends this through the webserver. Traditionally, and sensibly, the files served as web pages are owned by the author, readable and writable by them, the "group" user permissions are unset to not readable/writable/executable and generally not used for anything, and the "other" user permissions (i.e. everyone else) are read-only. The web server reads those files as the other user, since everyone else on the internet is not the owner of the files, and should only have read-access. This gets more difficult with authoring programs (WordPress, Joomla, etc), trying to get them to work in that model. Quite why they don't understand they need to work that way eludes me. People often end up setting their files as world-writable by virtue of getting ownership and permissions wrong. e.g. They make the files readable and writeable and owned by Apache or WordPress. Now the thing that should only be reading the files to serve them, can modify them. And unknown users on the internet can modify them with carefully crafted URLs. -- uname -rsvp Linux 3.10.0-1160.92.1.el7.x86_64 #1 SMP Tue Jun 20 11:48:01 UTC 2023 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list.

Even when just "trying it out" one should do it with full security applied at all levels -- network/system/application. Adding security back in at the end generally results in something that's not well considered or integrated. This approach often leaves security holes or making security compromises because something that "worked", in an insecure environment, doesn't when appropriate security is applied. Also, *never* turn off security contexts/options just because you don't understand them, figure them out instead. Lowering security will invariably come back to haunt.

On 7/21/2023 1:47 AM, Peter Boy wrote: Would it be better in the future to use threads on the server list? This thread is beginning to get a bit old. I would think server experimentation would be better at the server list. B